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) support #439

Closed
bricss opened this issue Oct 12, 2015 · 19 comments
Closed

SHA-3 (Keccak) support #439

bricss opened this issue Oct 12, 2015 · 19 comments
Labels
issue: feature request The issue was opened to request a feature

Comments

@bricss
Copy link

bricss commented Oct 12, 2015

Add support of new standardized SHA-3 hash algorithm.

Since FIPS has released it as a standard:
http://csrc.nist.gov/groups/ST/hash/sha-3/sha-3_standardization.html
http://keccak.noekeon.org/fips202final.html

@GamePad64
Copy link

Well, it would be very good.

@le4ker
Copy link

le4ker commented Dec 24, 2015

👍

@ladar
Copy link

ladar commented Dec 29, 2015

I'd like to see this as well. I'm curious if it's even on the roadmap? It will need to be added eventually, so I'm wondering if the plan is to be preemptive, or wait until an IETF RFC (like TLS or DANE) requires it? The 1.1.0 branch seems like a good place to start experimenting with support for it (even if it just a low level interface for now, and not all the way up the stack to the EVP/BIO layers).

@joostrijneveld
Copy link

I agree that having SHA-3 available as a basic primitive available through sha.h would already be helpful, even if not yet implemented throughout the rest of the library.

@richsalz
Copy link
Contributor

It is not on the roadmap for 1.1; we've got too much other stuff to do. The only way it could possibly happen is if someone provides code that's integrated and consistent with the rest of openssl.

@mattcaswell mattcaswell added the issue: feature request The issue was opened to request a feature label May 16, 2016
@mattcaswell mattcaswell added this to the Post 1.1.0 milestone May 16, 2016
@robertwagner
Copy link

robertwagner commented Sep 19, 2016

@ladar
Copy link

ladar commented Oct 24, 2016

Just tickling this ticket since it looks like the keccak primitives got merged into master with c3086f4, But alas, they aren't integrated up the API stack yet. I'm tempted to give it a shot, but thought others on this thread might have more time/experience then myself.

@mattcaswell
Copy link
Member

I suspect @dot-asm has this on his roadmap.

@richsalz
Copy link
Contributor

It’s being worked on….

@ladar
Copy link

ladar commented Oct 26, 2016

Hi @richsalz is there a fork (or branch) you can point me at where this work is occurring?

@levitte
Copy link
Member

levitte commented Oct 26, 2016

@ladar, there isn't one yet.

@richsalz
Copy link
Contributor

No. Everything that will end up in OpenSSL is done as PR's, so just watch. Or make your own PR :)

@ladar
Copy link

ladar commented Oct 28, 2016

I get that everything is happening via pull requests. I was just wondering if there was a repo/fork you knew about that made progress beyond what @dot-asm has submitted? I was looking for something that offered integration with the higher level interfaces... if one does pop up, let me know, and/or tickle this thread...

I tried searching on my own but got nada... and the fork summary page, which will sometimes help point to external repos with improvements, doesn't work for OpenSSL. You're too popular.

https://github.com/openssl/openssl/network

@mattcaswell
Copy link
Member

You've seen this right?

https://github.com/openssl/openssl/blob/master/crypto/sha/keccak1600.c

Nothing in the public header files yet though, but a work in progress.

@ladar
Copy link

ladar commented Nov 26, 2016

Hi @mattcaswell ... yes, I have looked at the referenced file, and the keccak implementation. My comment was in regards to whether a branch/fork existed where someone had added support to the higher level interfaces, like the EVP_() and HMAC_() functions, or definitions to the obj_mac.h file, etc.

P.S. My comment about Ed25519 a couple of hours ago was intended for the Ed25519 issue (and not SHA3), so I apologize for posting it here by mistake.

@joshfaust
Copy link

Has there been any movement on this? Would love to see SHA3 implemented.

@richsalz
Copy link
Contributor

richsalz commented Jun 14, 2017 via email

@kroeckx
Copy link
Member

kroeckx commented Jul 5, 2017

I think the current state is that the algorithms itself are included, but that all the EVP related changes are missing like having an EVP_sha3_256().

@richsalz
Copy link
Contributor

all done.

openssl-machine pushed a commit to openssl/web that referenced this issue Nov 14, 2023
Signed-off-by: Anton Arapov <anton@openssl.org>

Reviewed-by: Tim Hudson <tjh@openssl.org>
Reviewed-by: Tomas Mraz <tomas@openssl.org>
(Merged from openssl/openssl#439)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue: feature request The issue was opened to request a feature
Projects
None yet
Development

No branches or pull requests