Catch up to the h2c and ecvrf IETF drafts #114
Merged
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
Nothing meaningful has changed here.
2 tasks
Because the draft authors decided to add Y to the challenge generation input in v11, this breaks output compatibility. If you need the previous semantics (for compatibility for example), use `Prove_v10`, `Verify_v10`, `ProveWithAddedRandomness_v10`. Note that with the v11 (and later) semantics, pi will change for a given key + message tuple, while beta will remain unchanged, thus there is only one `ProofToHash` routine.
Yawning
force-pushed
the
yawning/feature/ietf-catchup
branch
from
518563e to
2879729
Compare
abukosek
approved these changes
Jul 8, 2022
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.
There are no functional changes in the newer versions of the h2c draft for the suites we care about.
The ECVRF IETF draft broke proof backward compatibility as of v11, and we based the implementation off v10. As there are systems in production that use the v10 style proofs, backward compatibility APIs are needed. If people blindly bump the import, they will see undesirable behavior (old proofs will fail to verify etc), but surely people don't blindly bump dependencies right?