node 17.1 verify failure using https with pfx certificate

[introspection3]

Version

17.1

Platform

ubuntun 20 x64

Subsystem

No response

What steps will reproduce the bug?

if (sslConfig.type == 'pfx') {
    serverOptions = {
        pfx: fs.readFileSync(path.join(configDir, 'ssl', sslConfig.pfxName)),
        passphrase: sslConfig.pfxPassword
    };
}

let server = https.createServer(serverOptions, async function(req, res) {
           
});

How often does it reproduce? Is there a required condition?

every time

What is the expected behavior?

No response

What do you see instead?

pem works fine

Additional information

No response

[introspection3]

Node.js v17.0.1
node:internal/tls/secure-context:276
context.loadPKCS12(toBuf(pfx), toBuf(passphrase));
^

Error: unsupported
at configSecureContext (node:internal/tls/secure-context:276:15)
at Object.createSecureContext (node:_tls_common:116:3)
at Server.setSecureContext (node:_tls_wrap:1344:27)
at Server (node:_tls_wrap:1203:8)
at new Server (node:https:69:3)
at Object.createServer (node:https:105:10)
at createHttpProxy (/opt/fastnat/index.js:1728:28)
at /opt/fastnat/index.js:184906:1
at /opt/fastnat/index.js:184991:3
at Object. (/opt/fastnat/index.js:184994:12)

[tniessen]

Thank you for the report. Could you post information about the PFX file you are attempting to load, @564064202? For example, using OpenSSL, you can list the contents of the PKCS#12 structure without revealing secret keys.

openssl pkcs12 -info -in mycert.pfx -noout

This should print a list of objects and algorithms, e.g.,

MAC: sha1, Iteration 2048
MAC length: 20, salt length: 8
PKCS7 Encrypted data: pbeWithSHA1And3-KeyTripleDES-CBC, Iteration 2048
Certificate bag
PKCS7 Data
Shrouded Keybag: pbeWithSHA1And3-KeyTripleDES-CBC, Iteration 2048

[introspection3]

MAC: sha1, Iteration 1
MAC length: 20, salt length: 8
PKCS7 Encrypted data: pbeWithSHA1And40BitRC2-CBC, Iteration 2048
Certificate bag
Certificate bag
PKCS7 Data
Shrouded Keybag: pbeWithSHA1And3-KeyTripleDES-CBC, Iteration 2048

[introspection3]

@tniessen

MAC: sha1, Iteration 1
MAC length: 20, salt length: 8
PKCS7 Encrypted data: pbeWithSHA1And40BitRC2-CBC, Iteration 2048
Certificate bag
Certificate bag
PKCS7 Data
Shrouded Keybag: pbeWithSHA1And3-KeyTripleDES-CBC, Iteration 2048

[tniessen]

@564064202 The error is most likely due to the use of pbeWithSHA1And40BitRC2-CBC in the PKCS#12 file, in particular, because of RC2.

RC2 is disabled by default in Node.js 17 and can only be enabled through the legacy provider, see --openssl-legacy-provider.

However, before enabling the legacy provider, you should consider using a different cipher to protect your PKCS#12 files. RC2 is disabled because it is technically broken and because it has virtually no advantage over modern ciphers.

[introspection3]

@tniessen thank you sir,by the way ,where I can see every node version's changes?

[tniessen]

where I can see every node version's changes?

All releases are listed as GitHub releases in this repository, in the changelogs directory, and in the Node.js blog.

Additional information is sometimes available through the nodejs Twitter account and/or through Node.js medium.

In this case, the problem might have been difficult to track down since we did not actively disable RC2. Instead, as part of the transition to Node.js 17, we updated OpenSSL from 1.1 to 3.0, and OpenSSL 3 disabled many legacy algorithms, including RC2.

[tniessen]

Closing this issue as answered. Please let us know if the problem persists after switching to a supported cipher (or enabling the --openssl-legacy-provider option if switching to a different cipher is not possible).

[chucker]

For the curious: with OpenSSL 3, you can use a command like

openssl pkcs12 -in oldPfxFile.pfx -nodes -legacy | openssl pkcs12 -export -out newPfxFile.pfx

to modernize the cipher on your .pfx.