Skip to content
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

Closed
tiran opened this issue Aug 7, 2013 · 6 comments
Closed

SHA-3 (Keccak) #8

tiran opened this issue Aug 7, 2013 · 6 comments

Comments

@tiran
Copy link
Contributor

tiran commented Aug 7, 2013

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 .

@alex
Copy link
Member

alex commented Aug 7, 2013

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.

@lvh
Copy link
Member

lvh commented Aug 7, 2013

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.)

@lvh lvh closed this as completed Aug 7, 2013
@dstufft
Copy link
Member

dstufft commented Aug 7, 2013

Did you mean to close this @lvh?

@lvh
Copy link
Member

lvh commented Aug 7, 2013

Oops. I didn't know what you were talking about, I just didn't realize I had closed it. My bad :)

@lvh lvh reopened this Aug 7, 2013
@tiran
Copy link
Contributor Author

tiran commented Aug 7, 2013

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.

@alex
Copy link
Member

alex commented Oct 22, 2013

I think we're going to close this until SHA-3 is a standard.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

4 participants