You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OpenSSL supports "BEGIN TRUSTED CERTIFICATE", whereas Node.js silently ignores them. When people fail to authenticate with a ca: file, they often try with other tools (openssl s_client -CAfile ..., curl -cacert ..., ...) to confirm where the CAs are valid. They find they are, but that they don't work with Node.js. Ouch.
Support the same PEM certificate formats for the ca: option to
tls.createSecureContext() that are supported by openssl when loading a
CAfile.
Fixes: nodejs#24761
Support the same PEM certificate formats for the ca: option to
tls.createSecureContext() that are supported by openssl when loading a
CAfile.
Fixes: #24761
PR-URL: #24733
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
refack
pushed a commit
to refack/node
that referenced
this issue
Jan 14, 2019
Support the same PEM certificate formats for the ca: option to
tls.createSecureContext() that are supported by openssl when loading a
CAfile.
Fixes: nodejs#24761
PR-URL: nodejs#24733
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Support the same PEM certificate formats for the ca: option to
tls.createSecureContext() that are supported by openssl when loading a
CAfile.
Fixes: nodejs#24761
PR-URL: nodejs#24733
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
OpenSSL supports "BEGIN TRUSTED CERTIFICATE", whereas Node.js silently ignores them. When people fail to authenticate with a
ca:
file, they often try with other tools (openssl s_client -CAfile ...
,curl -cacert ...
, ...) to confirm where the CAs are valid. They find they are, but that they don't work with Node.js. Ouch.Fixed in #24733
The text was updated successfully, but these errors were encountered: