-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
crypto: add support for SHA3 #1315
Comments
Is SHA-3 even standardized yet? I don't think OpenSSL supports it yet either... |
Nope, it's not... |
I don't think we support anything in core that isn't in OpenSSL. We'll be upgrading to OpenSSL 1.0.2 soon, if that helps. (#589) |
Yes, I agree, I should to first check OpenSSL for SHA3 support. |
Just wanted to mention that Keccak support is in OpenSSL (but unreleased as of yet): openssl/openssl#439 so SHA3 will presumably get supported once the next OpenSSL gets out and Node upgrades to it. |
Please reopen, please see https://www.openssl.org/blog/blog/2018/09/11/release111/
|
@ppKrauss have you tried node 11.9.0? |
Thanks @sam-github , seems the problem... How to check my crypto-module version? |
Sorry @sam-github , now is working! UBUNTU Any clues about this question, "how to check crypto module version?" |
|
It's in mind to implement that on previous LTS versions? I am in 8.12.0 |
@RSginer OpenSSL 1.1.1 has already been backported to v10.x and will be in the next v10.x release. v8.x still only has OpenSSL 1.0.2 and there is no PR to backport OpenSSL 1.1.1 to that branch yet. It's unlikely v8.x will get it as it's been in maintenance mode since the beginning of this year and will EOL in December. |
@mscdex great! Thanks a lot |
I'm not sure that this made it in. I updated to 10.15.3 and there's no sha-3
|
@troppoli You will find it in Node.js >= 12 |
@bricss @RSginer Sorry for the fire drill, my update to latest didn't get me the latest in LTS 10.16.0, and that does have sha-3
|
It would be great to add support for SHA3 (Keccak) algorithm to crypto.createHash, cause NIST has approved it in back October 2012 and we need to install third-party extensions in our days to use it.
The text was updated successfully, but these errors were encountered: