Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[v16.x] src: add --openssl-legacy-provider option #42972

Closed
wants to merge 1 commit into from

Commits on Jun 23, 2022

  1. src: add --openssl-legacy-provider option

    This commit adds an option to Node.js named --openssl-legacy-provider
    and if specified will load OpenSSL 3.0 Legacy provider when dynamically
    linking Node.js v16.x with OpenSSL 3.0.
    
    Building:
    $ ./configure --shared-openssl \
     --shared-openssl-libpath=/path/openssl_quic-3.0/lib64 \
     --shared-openssl-includes=/path/openssl_quic-3.0/include \
     --shared-openssl-libname=crypto,ssl
    $ make -j8
    
    Verify options is available:
    $ ./node --help
    ...
    --openssl-legacy-provider  enable OpenSSL 3.0 legacy provider
    
    Usage:
    $ export LD_LIBRARY_PATH=/path/openssl_quic-3.0/lib64
    $ export OPENSSL_MODULES=/path/openssl_quic-3.0/lib64/ossl-modules/
    $ export OPENSSL_CONF=/path/openssl_quic-3.0/ssl/openssl.cnf
    $ ./node --openssl-legacy-provider  -p 'crypto.createHash("md4")'
    Hash {
      _options: undefined,
      [Symbol(kHandle)]: Hash {},
      [Symbol(kState)]: { [Symbol(kFinalized)]: false }
    }
    
    Fixes: nodejs#40948
    
    Refs: nodejs#40455
    PR-URL: nodejs#40478
    Reviewed-By: Richard Lau <rlau@redhat.com>
    Reviewed-By: Tobias Nießen <tniessen@tnie.de>
    danbev committed Jun 23, 2022
    Configuration menu
    Copy the full SHA
    219e4f9 View commit details
    Browse the repository at this point in the history