-
Notifications
You must be signed in to change notification settings - Fork 151
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
feat: support Keccak with sha3 #737
Conversation
Yo any update on this? |
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.
lgtm impl wise, pending either @DaniPopes or @mattsse if we want this in
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.
tbh not super familiar with the diff, but do they even produce the same hashes?
yeah they do produce the same hashes, both crates are impls of https://csrc.nist.gov/pubs/fips/202/final |
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.
not opposed to it, but defer to @DaniPopes
1 question about activated both feature gated hashers
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.
Thanks! I've simplified the cfgs by consolidating them into one place
Adds a new feature
sha3-keccak
toalloy-primitives
that when enabled, usessha3
for Keccak. This can be desirable as in some casessha3
is faster.This feature is added in a completely backward-compatible way:
tiny-keccak
is still the default, and downstream libs/apps will not suddenly start usingsha3
by just doingcargo update
.