-
Notifications
You must be signed in to change notification settings - Fork 30
Normalize EC2 key size at input time to ensure RFC 9053 compliance #223
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
kentakayama
wants to merge
9
commits into
veraison:main
Choose a base branch
from
kentakayama:normalize-ec2-key-size
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+138
−34
Open
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
cb33f56
update: always handle x, y and d with full size for the curve
kentakayama 1337f29
add: test ensuring the NewKeyEC2 always returns correct byte size of …
kentakayama f3b1be1
add: failure test ensuring invalid size of x and d for OKP
kentakayama b9d3c0b
update: Normalize and validate EC2 key lengths to ensure compliance w…
kentakayama 52af599
fix: typo
kentakayama 88057f2
refactor: clarify error handling for missing vs malformed params for …
kentakayama 13e02ff
refactor: comments
kentakayama b745bfa
refactor: split curveSize into keySizeEC2 and keySizeOKP
kentakayama be9afe2
fix: bug in validate() with length 0 slice
kentakayama File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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 file contains hidden or 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
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 was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you explain why these changes were necessary?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(I'm sorry -- while checking this error case, I also fixed a bug introduced by me in be9afe2 while checking this error case.)
As I mentioned here, I think it is important to distinguish between:
[]byte(i.e.nil), and[]bytewhose length is 0.The following test demonstrates the differences clearly:
With previous implementation, all of these cases produced the same error:
This Pull Request updates the behavior so that cases where a non-nil but empty (does not match to the expected size) slice is produced are reported more accurately: