kem/hybrid: Remove restriction on seed sizes #342
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
None of the implemented KEMs aim above 256 bits of security and so SHAKE256 (easily) suffices to stretch one seed into two.
|
I thought about adding a |
|
Another solution I thought about is to simply change our schemes to use ≤32 byte seeds, but that might break existing users and would require an extra function to reproduce the test vectors that come with the implementations. |
armfazh
approved these changes
Jun 28, 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.
None of the implemented KEMs aim above 256 bits of security and so SHAKE256
(easily) suffices to stretch one seed into two.