-
Notifications
You must be signed in to change notification settings - Fork 964
Expose blst internals #6829
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
Merged
Merged
Expose blst internals #6829
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
4e8f826
expose `point` and `from_point` on `GenericSignature`
dknopik dfd7ab0
add `point` and `from_point` to `GenericSecretKey`
dknopik 5dfda40
add `serialize_uncompressed` to `GenericSignature`
dknopik f551579
add `deserialize_uncompressed` to `GenericSignature`
dknopik 87515cc
actually add `deserialize_uncompressed` to `GenericSignature`
dknopik a714c14
cargo fmt
dknopik 65120a6
Merge branch 'unstable' into expose-blst-internals
dknopik b54cea9
take reference in from_point
dknopik 246108b
provide from_point only if `Sec: Clone`
dknopik 04205ed
cargo fmt
dknopik 4ca8823
check for uncompressed infinity signatures
dknopik ec06b3b
add test for hardcoded infinity sigs
dknopik 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
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
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 elaborate on this? Is it because zeroize only happens on drop, and a move is implemented as a memcpy without a drop?
Uh oh!
There was an error while loading. Please reload this page.
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.
Exactly.
Cloning here ensures that we have two owned
blst::min_pk::SecretKey, which will be zeroed each on drop. Moving may or may not do a memcpy (up to rustc to inline or do other optimisations), and may cause data to be left behind.See also: https://docs.rs/zeroize/latest/zeroize/index.html#stackheap-zeroing-notes
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 suspect there are other places we've run afoul of this. Good to know.
I wonder how invasive it would be to use
Pinon secret keys. Might be an exploration for another day