-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
SHA-3 (Keccak) #8
Comments
IMO we should wait until it's finalized (I assume that's why OpenSSL doesn't have it yet). Happy to heart other opinions though. |
If we include hash functions where internal state != digest value, please also provide an API for getting and setting the internal state. I don't care if it optionally raises on some implementations, but just provide the API. Without this, it's impossible to write half-decent hash chains using these hash functions. (I think that's a misfeature anyway; the old way is only bad if you abuse hash functions and have no clue what you're doing.) |
Did you mean to close this @lvh? |
Oops. I didn't know what you were talking about, I just didn't realize I had closed it. My bad :) |
Interesting idea ... SHA-3 objects aren't pickle-able because the code doesn't expose their internal state. I never thought of that. I'm going to talk to A.M. Kuchling about it. |
I think we're going to close this until SHA-3 is a standard. |
I'm the author of Python 3.4's sha3 module and https://bitbucket.org/tiran/pykeccak/ . OpenSSL doesn't provide SHA-3 yet. I'm willing to re-license and adapt my code for cryptography if you are interested in SHA-3 support.
SHA-3 is not finalized yet so we may want to wait, see http://bugs.python.org/issue16113 and http://csrc.nist.gov/groups/ST/hash/sha-3/timeline_fips.html .
The text was updated successfully, but these errors were encountered: