Update for SPAKE2 #294
Merged
Update for SPAKE2 #294
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
|
This should be ready for review. |
baylesj
reviewed
Mar 31, 2023
markafoltz
added
v1-spec
security-tracker
|
PTAL @baylesj |
|
Went ahead and merged this as outstanding comments are addressed. Let me know if there are further comments @baylesj |
github-actions bot
added a commit
that referenced
this pull request
Feb 28, 2024
SHA: d338b24 Reason: push, by mfoltzgoogle Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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 addresses Issue #235: Update SPAKE2 section according to current IETF draft
The IETF draft has had several updates since the SPAKE2 section was first written. I am taking this opportunity to align
the protocol with the way the algorithm is written in the current draft, as an explicit two-round process.
By moving to a two-round process the
auth-spake2-needs-pskmessage can be eliminated and replaced by having each agent explicitly state the PSK status in theauth-spake2-handshakemessage. This leads to a cleaner and easier to understand protocol.In addition the message fields and associated text are updated to align with the terms used in the IETF draft.
Finally it updates the transcript-mac field to 64 bytes to allow the use of SHA-512 in the HMAC.
Preview | Diff