I am not 100% sure about patching nodejs; using a config file is documented behavior:
- https://nodejs.org/api/cli.html#--openssl-configfile - https://nodejs.org/api/cli.html#openssl_conffile
So if you do patch it this way, then at least the logic should be to e.g. call OPENSSL_no_config iff the env var OPENSSL_CONF is empty and no --openssl-config is given (in order to allow users to still explicitly pass a config).
I am not 100% sure about patching nodejs; using a config file is documented behavior:
- https:/ /nodejs. org/api/ cli.html# --openssl- configfile /nodejs. org/api/ cli.html# openssl_ conffile
- https:/
So if you do patch it this way, then at least the logic should be to e.g. call OPENSSL_no_config iff the env var OPENSSL_CONF is empty and no --openssl-config is given (in order to allow users to still explicitly pass a config).