-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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.getCiphers()
includes unsupported ciphers
#41857
Comments
FWIW I think calling the various |
@nodejs/crypto |
I figured out what was happening, I have a potential solution incoming.... |
Fixes: nodejs#41857 PR-URL: nodejs#41864 Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Filip Skokan <panva.ip@gmail.com>
Fixes: nodejs#41857 PR-URL: nodejs#41864 Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Filip Skokan <panva.ip@gmail.com>
Fixes: nodejs#41857 PR-URL: nodejs#41864 Reviewed-By: Tobias Nießen <tniessen@tnie.de> Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Filip Skokan <panva.ip@gmail.com>
@noscripter You'll have to provide more details. I cannot duplicate the issue of |
Version
v17.x, master
Platform
n/a
Subsystem
crypto
What steps will reproduce the bug?
$ node -e 'console.log(crypto.getCiphers().includes("rc4")); crypto.createCipheriv("rc4", Buffer.alloc(16), Buffer.alloc(0))'
How often does it reproduce? Is there a required condition?
Yes.
What is the expected behavior?
What do you see instead?
Additional information
Node.js shouldn't fib about its supported ciphers.
Whatever change is made for
crypto.getCiphers()
should probably also be made for the othercrypto.get*()
methods for consistency.The text was updated successfully, but these errors were encountered: