deps,build: add OpenSSL building of legacy module

[danbev]

This commit adds a configuration time flag to enable OpenSSL legacy
module to be built.

For example, the following will build the legacy module:

$ ./configure --openssl-legacy-module

To enable the default provider one has currently has to update the
OpenSSL configuration file, openssl.cnf:

[openssl_init]providers = provider_sect[provider_sect]default = default_sectlegacy = legacy_sect[default_sect]activate = 1[legacy_sect]activate = 1

This module can then be used by specifying the environment variable
OPENSSL_MODULES like this:

$ env OPENSSL_MODULES=$PWD/out/Release/obj.target/deps/openssl/lib/openssl-modules OPENSSL_CONF=out/Release/obj.target/deps/openssl/openssl.cnf ./node -p 'crypto.createHash("md4")'Hash { _options: undefined, [Symbol(kHandle)]: Hash {}, [Symbol(kState)]: { [Symbol(kFinalized)]: false }

Refs: #40455

[targos]

Does it allow to use md4 again by default?

[danbev]

Does it allow to use md4 again by default?

No, but I'm currently looking into enabling/configuring the legacy provider which does support md4. I've not got that part working yet though so I'll convert this into a draft pr.

[tniessen]

Thank you @danbev!

[nodejs-github-bot]

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

[danbev]

Does it allow to use md4 again by default?

I'm afraid this does not allow the legacy provider to be enabled by default, instead the user would need to go through the steps above in the PR description.

[mhdawson]

I'm guessing it does not make sense for this to have danielbevenius in the path. Same for the next line.

[mhdawson]

Although that may be a more general comment since it's not a change in this PR

[danbev]

I've taken a look at this and I'm not sure how I can prevent this in Perl. I'll take another look but I don't think this is critical as my understanding is that after we generate this file we only use it to parse out values. Still I'd rather fix this but not sure how at the moment.

[richardlau]

I assume the paths with be more generic (but still absolute) if regenerating the config via the Docker file?

node/Makefile

Lines 1479 to 1481 in ed01811

	gen-openssl: ## Generate platform dependent openssl files (requires docker)
	docker build -t node-openssl-builder deps/openssl/config/
	$(DOCKER_COMMAND) node-openssl-builder make -C deps/openssl/config

[danbev]

#40478 has been opened and contains a suggestion by @richardlau to statically link the legacy provider and allow it to be enabled by a command line flag instead of dynamically linking which is done in this pull request.

[danbev]

I'm closing this in favor of #40478.