-
Notifications
You must be signed in to change notification settings - Fork 46
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
The ca option is not passed to node-socket instances #66
Comments
ca
option is not passed to node-socket instances
Fixed by #67 The webpack version installed by running |
The node socket does not consume this option... Add the missing cert to your cert store intead. |
True, but Last entry for tls.connect options. |
Firefox CA store does not have any influence on your systen cert store because Firefox brings its own store. Use the keychain (on macOS) or whatever your respective system uses. |
node.js uses its own certificate store (with certificates copied from the Mozilla CA Certificate Store) by default, as mentioned on the tls page: While installing the certificate on the OS level could* solve the problem, it's also a security risk to accept all certificates from a CA you otherwise wouldn't trust. With the ca option, you only have trust the issuer where it's needed. * I'm not sure if node.js uses both the internal cert store and the OS provided certificates |
CA certificates are not passed to the
net.tls.connect()
function and the socket can not be upgraded if the server uses a certificate that is not in the mozilla CA Certificate Store.Use-case: IMAP connection using emailjs-imap-client to internal servers.
The text was updated successfully, but these errors were encountered: