chore!: align to draft 16, update dependencies #365
Merged
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 updates the implementation to (actually) match the draft 16 of the protocol. Most notable (and breaking) change is the change of the context string to
OPAQUEv1-
. Terminology around aPAKE has been updated to match the changes done in the draft as well (from asymmetric to augmented).I've also tweaked the cargo deny config to get it working on newer versions (as well as bumping the action to v2), and ditched unmaintained json dependency in favor of serde_json.
Side note, that is probably more of a protocol-level nit than something to do with the lib: RFC 9497 (OPRF) uses an uppercase V1, whereas OPAQUE uses a lowercase v. Very specific, but an inconsistency nonetheless 😄