Replies: 1 comment 3 replies
-
I can't speak to nmap but browers as a rule don't support insecure ciphers, and that's most TLSv1.0 ciphers at this point. You should be able to connect with |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm using Node.js 18.12.1 (Windows 10) and would like to create a https server which supports TLS 1.0 (for compatibility reasons).
However all attempts to enable support for obsolete protocols failed, and I tend to think that this version of Node.js doesn't support them at all.
Here is the minimal code to test the behavior:
Needed files
localhost.key
andlocalhost.crt
can be generated withopenssl
(reference):The content of
localhost.conf
is as follows:I verify protocols support with
nmap
(download for Windows) and typical output fornmap --script ssl-enum-ciphers -p 9999 localhost
is as follows (TLS 1.2 is minimum by default in Node.js):What I'v tried so far:
httpsOptions
(settingsecureProtocol: 'TLSv1_server_method'
, and alike) - it causesERR_SSL_VERSION_OR_CIPHER_MISMATCH
(in the browser) andnmap
shows no ciphers at all.node --tls-min-v1.0 server.js
- see Expose a way to specify TLS version by node command line #27666 ) - it has no effect and Node.js runs with same set of protocols.Do I miss something?
Any hints on enabling TLS 1.0 in Node.js?
Beta Was this translation helpful? Give feedback.
All reactions