Adding distinction between 3-message and 2-message protocol in design differences section #454
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… differences section
kevinlewi
force-pushed
the
add_message_distinction
branch
from
c4dc5b1 to
4cc8280
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a clarifying note that the original OPAQUE protocol described a 2-message protocol, but the one presented in this draft is a 3-message version. This is under the "Notable Design Differences" section.
It also adds a reference to the full version of the OPAQUE paper (https://eprint.iacr.org/2018/163) where the 3-message protocol is analyzed.