src,deps,build,test: add OpenSSL config appname

[danbev]

This commit adds the setting of an appname (configuration section
name), nodejs_conf, to be used when reading OpenSSL configuration
files.

The motivation for this is that currently the default OpenSSL
configuration, openssl_conf, element will be used which may be
undesirable as it might configure OpenSSL in unwanted ways. With this
commit it is still possible to use a default openssl.cnf file but the
only section that Node.js will read from is a section named
nodejs_conf.

Refs: #40366

[nodejs-github-bot]

Review requested:

• @nodejs/gyp
• @nodejs/startup

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/44049/

[mhdawson]

@danbev this will be breaking for anybody currently depending on the default config right?

[danbev]

this will be breaking for anybody currently depending on the default config right?

Yeah, this will probably break for them and they would have to copy, or rename, the default section/appname from openssl_conf to nodejs_conf.

[BethGriggs]

Could/should we also add a flag to allow the old behaviour of loading from the shared section of the OpenSSL config? (maybe --openssl-shared-config or something more suitably named?)

[danbev]

Could/should we also add a flag to allow the old behaviour of loading from the shared section of the OpenSSL config? (maybe --openssl-shared-config or something more suitably named?)

82c3f44 contains your suggestion (at least my interpretation :) for adding such a flag.

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/44060/

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/44063/

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/44073/

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/44143/