test: update tests for OpenSSL 3.0.14

[richardlau]

Starting from OpenSSL 3.0.14, 3.1.6, 3.2.2, and 3.3.1, OpenSSL was fixed to return an error reason string for bad/unknown application protocols.

Update tests to handle both the old ECONNRESET error on older versions of OpenSSL and the new ERR_SSL_TLSV1_ALERT_NO_APPLICATION_PROTOCOL on newer versions of OpenSSL.

Refs: openssl/openssl#24338

---

Addresses these failures (Node.js dynamically linked against OpenSSL 3.0.14 -- I first noticed these (and other failures) with OpenSSL 3.2.2):

not ok 1779 parallel/test-http2-https-fallback --- duration_ms: 164.14700 severity: fail exitcode: 1 stack: |- node:assert:126 throw new AssertionError(obj); ^ AssertionError [ERR_ASSERTION]: Expected values to be strictly equal: + actual - expected + 'ERR_SSL_TLSV1_ALERT_NO_APPLICATION_PROTOCOL' - 'ECONNRESET' at TLSSocket.<anonymous> (/home/nodejs/node/test/parallel/test-http2-https-fallback.js:154:11) at TLSSocket.<anonymous> (/home/nodejs/node/test/common/index.js:466:15) at TLSSocket.emit (node:events:520:28) at emitErrorNT (node:internal/streams/destroy:170:8) at emitErrorCloseNT (node:internal/streams/destroy:129:3) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) { generatedMessage: true, code: 'ERR_ASSERTION', actual: 'ERR_SSL_TLSV1_ALERT_NO_APPLICATION_PROTOCOL', expected: 'ECONNRESET', operator: 'strictEqual' } Node.js v23.0.0-pre ...--not ok 1873 parallel/test-http2-server-unknown-protocol --- duration_ms: 132.88000 severity: fail exitcode: 1 stack: |- node:assert:126 throw new AssertionError(obj); ^ AssertionError [ERR_ASSERTION]: Expected values to be strictly equal: + actual - expected + 'ERR_SSL_TLSV1_ALERT_NO_APPLICATION_PROTOCOL' - 'ECONNRESET' at TLSSocket.<anonymous> (/home/nodejs/node/test/parallel/test-http2-server-unknown-protocol.js:45:12) at TLSSocket.<anonymous> (/home/nodejs/node/test/common/index.js:466:15) at TLSSocket.emit (node:events:520:28) at emitErrorNT (node:internal/streams/destroy:170:8) at emitErrorCloseNT (node:internal/streams/destroy:129:3) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) { generatedMessage: true, code: 'ERR_ASSERTION', actual: 'ERR_SSL_TLSV1_ALERT_NO_APPLICATION_PROTOCOL', expected: 'ECONNRESET', operator: 'strictEqual' } Node.js v23.0.0-pre ...--not ok 3010 parallel/test-tls-alpn-server-client --- duration_ms: 156.74900 severity: fail exitcode: 1 stack: |- node:assert:126 throw new AssertionError(obj); ^ AssertionError [ERR_ASSERTION]: Expected values to be strictly equal: + actual - expected + 'ERR_SSL_TLSV1_ALERT_NO_APPLICATION_PROTOCOL' - 'ECONNRESET' at TLSSocket.<anonymous> (/home/nodejs/node/test/parallel/test-tls-alpn-server-client.js:195:14) at TLSSocket.<anonymous> (/home/nodejs/node/test/common/index.js:466:15) at TLSSocket.emit (node:events:520:28) at emitErrorNT (node:internal/streams/destroy:170:8) at emitErrorCloseNT (node:internal/streams/destroy:129:3) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) { generatedMessage: true, code: 'ERR_ASSERTION', actual: 'ERR_SSL_TLSV1_ALERT_NO_APPLICATION_PROTOCOL', expected: 'ECONNRESET', operator: 'strictEqual' } Node.js v23.0.0-pre ...

cc @nodejs/crypto

[nodejs-github-bot]

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

[nodejs-github-bot]

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

[nodejs-github-bot]

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

[mhdawson]

LGTM

[tniessen]

@richardlau Is there any chance you could make this conditional based on the version of OpenSSL? Otherwise, we'll likely forget about it and keep the old code here forever.

[richardlau]

@richardlau Is there any chance you could make this conditional based on the version of OpenSSL? Otherwise, we'll likely forget about it and keep the old code here forever.

It's going to be complicated -- there's currently four OpenSSL 3 lines:

• 3.0.x
• 3.1.x
• 3.2.x
• 3.3.x

and the change is only in the latest release of each of those four lines.

[richardlau]

@richardlau Is there any chance you could make this conditional based on the version of OpenSSL? Otherwise, we'll likely forget about it and keep the old code here forever.

@tniessen We'd end up with code like this repeated for each of the three tests:

diff --git a/test/parallel/test-http2-https-fallback.js b/test/parallel/test-http2-https-fallback.js
index 8e0612375f4..8a1c06caad4 100644
--- a/test/parallel/test-http2-https-fallback.js+++ b/test/parallel/test-http2-https-fallback.js@@ -151,7 +151,14 @@ function onSession(session, next) {
// Incompatible ALPN TLS client
tls(Object.assign({ port, ALPNProtocols: ['fake'] }, clientOptions))
.on('error', common.mustCall((err) => {
- strictEqual(err.code, 'ECONNRESET');+ // ECONNRESET prior to OpenSSL 3.0.14, 3.1.6, 3.2.2, and 3.3.1.+ const { OPENSSL_VERSION_NUMBER } = require('node:crypto').constants;+ const expectedErr = (OPENSSL_VERSION_NUMBER < 0x300000e0 ||+ (OPENSSL_VERSION_NUMBER >= 0x30100000 && OPENSSL_VERSION_NUMBER < 0x30100060) ||+ (OPENSSL_VERSION_NUMBER >= 0x30200000 && OPENSSL_VERSION_NUMBER < 0x30200020) ||+ (OPENSSL_VERSION_NUMBER >= 0x30300000 && OPENSSL_VERSION_NUMBER < 0x30300010)) ?+ 'ECONNRESET' : 'ERR_SSL_TLSV1_ALERT_NO_APPLICATION_PROTOCOL';+ strictEqual(err.code, expectedErr);
cleanup();
testNoALPN();
}));

If you think this is worth doing I can update this PR, but I think this is harder to read.

[tniessen]

@richardlau It's entirely up to you :)

[richardlau]

@richardlau It's entirely up to you :)

In which case I'll land as-is as this has a passing CI, approvals and no blocks 🙂.

[nodejs-github-bot]

Landed in 14863e8

[lheckemann]

Older versions do fail the tests against newer OpenSSL versions, so could this be backported to v18 and v20?

[richardlau]

Older versions do fail the tests against newer OpenSSL versions, so could this be backported to v18 and v20?

Once it's gone out in a current (i.e. Node.js 22) release first.