-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
Expose a way to specify TLS version by node command line #27666
Comments
The following CLI flags are available for current versions of Node:
Do any of these look like what you need? |
Hi Team, |
It's under discussion, see #27432 (comment) (cc @sam-github) I'll close this out as answered. |
Reopened to track this as a feature (rather than making another). These are meaningful for 10.x, so I can implement them (hopefully fairly easily, I'll take a look today or tomorrow):
While TLS1.3 does not exist for 10.x, what about I can either:
|
@devanshu1111 ☝️ opinions as to what would be helpful to you? |
Thanks for looking into this. |
Thanks, please let us know the specific version under 10.x when it gets implemented. |
These options in exist in Node.js 12 (https://nodejs.org/dist/latest-v12.x/docs/api/cli.html#cli_tls_max_v1_2). The last ask in this issue was to backport to Node.js 10, which is now End-of-life. edit: scratch that - they were shipped in v10.20.0 via #27946 |
whats the flag for node 14.16.0 ?? |
Is your feature request related to a problem? Please describe.
Yes, we want to be TLS1.2 compliant. Checking the whole repository to make the whole code TLS1.2 complaint. We liked the existing idea of specifying cipher suit at "node --tls-cipher-list="ECDHE-RSA-AES128-SHA" server.js". We need similar command to specify TLS version.
Describe the solution you'd like
To specify the TLS version at node commandline. Similar to "node --tls-cipher-list="ECDHE-RSA-AES128-SHA" server.js"
Describe alternatives you've considered
Please describe alternative solutions or features you have considered.
The text was updated successfully, but these errors were encountered: