-
Notifications
You must be signed in to change notification settings - Fork 6
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
Add support for CSHAKE #80
Merged
Changes from 10 commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
83d99b3
add support for CSHAKE
qmuntal 804906f
Update cng/hash.go
qmuntal c95a35f
add Supports* functions
qmuntal 2998579
Merge branch 'cshake' of https://github.com/microsoft/go-crypto-winna…
qmuntal 77726dd
improve skips
qmuntal 029af55
refactor pure SHA3 API
qmuntal be8db59
speed-up sha3 reset
qmuntal 74f51cc
deduplicate code
qmuntal 9b21315
fix hashX.Clone
qmuntal 34746fe
Update cng/hash.go
qmuntal b09ee97
PR comments
qmuntal f7a768e
Merge branch 'cshake' of https://github.com/microsoft/go-crypto-winna…
qmuntal 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 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 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
Oops, something went wrong.
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.
This pattern seems like it makes it easier to spot bad access vs. sprinkling
runtime.KeepAlive
, why the change? (Also IMO would be good for golang-fips/openssl#238 (review).)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.
It is easy to forget to use
withCtx
(it happened in the OpenSSL module), so it is not a silver bullet. I prefer theruntime.KeepAlive
pattern because it doesn't add a nested block on each function that access the context (thus the code is simpler), and also to keep consistency with other algorithms, which tend to use theruntime.KeepAlive
rather than customwithX
functions.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.
Ok, if withCtx didn't help in practice, I agree that simplifying to
runtime.KeepAlive
makes sense. (If it did help, I would have said that it would make sense to expand that style to other algorithms as the way to get to consistency. 😄)