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
This issue is a request to update node and build it with the new flag --use-openssl-ca to use openssl's certificate store
Explaination
The default behavior for Nodejs is to bundle a snapshot of Mozilla CA (certificate authority) store into the build. This means that the default CA store is fixed upon building node. This is also not very helpful for non standard CA's.
As of Node 7.5.0 and the future release 6.11.0 node can be built to use openssl's certificate store
From node's build script readme file:
Using OpenSSL store allows for external modifications of the store. For most
Linux and BSD distributions, this store is maintained by the distribution
maintainers and system administrators. OpenSSL CA store location is dependent on
configuration of the OpenSSL library but this can be altered at runtime using
environmental variables.
Reference
Openssl CA support for Nodejs 7.5.0: node pull 8334
Node 6.11.0 proposal including the fix for the LTS verison: node pull 13059
The text was updated successfully, but these errors were encountered:
removed "update" label since we now build v6.11.4 which has this feature (if we need to modify the build) -- when this issue was first written we needed to update to at least 6.11.0 and then add the enhancement
This issue is a request to update node and build it with the new flag
--use-openssl-ca
to use openssl's certificate storeExplaination
The default behavior for Nodejs is to bundle a snapshot of Mozilla CA (certificate authority) store into the build. This means that the default CA store is fixed upon building node. This is also not very helpful for non standard CA's.
As of Node 7.5.0 and the future release 6.11.0 node can be built to use openssl's certificate store
From node's build script readme file:
Reference
Openssl CA support for Nodejs 7.5.0: node pull 8334
Node 6.11.0 proposal including the fix for the LTS verison: node pull 13059
The text was updated successfully, but these errors were encountered: