`parallel/test-tls-ocsp-callback` fails with OpenSSL 3.6.0

[richardlau]

When Node.js (current main) is built dynamically linked against OpenSSL 3.6.0, I'm seeing one test failure in parallel/test-tls-ocsp-callback (Linux x64).

nodejs@fec15585680c:~/node$ out/Release/node -p process.versions.openssl
3.6.0
nodejs@fec15585680c:~/node$ out/Release/node --test-reporter=./test/common/test-error-reporter.js --test-reporter-destination=stdout /home/nodejs/node/test/parallel/test-tls-ocsp-callback.js
/home/nodejs/node/test/parallel/test-tls-ocsp-callback.js:93
        assert.strictEqual(resp.toString(), testOptions.response);
                                ^

TypeError: Cannot read properties of null (reading 'toString')
    at TLSSocket.<anonymous> (/home/nodejs/node/test/parallel/test-tls-ocsp-callback.js:93:33)
    at TLSSocket.<anonymous> (/home/nodejs/node/test/common/index.js:475:15)
    at TLSSocket.emit (node:events:508:28)
    at TLSWrap.onocspresponse (node:internal/tls/wrap:441:22)

Node.js v25.0.0-pre
nodejs@fec15585680c:~/node$

cc @nodejs/crypto

While we have no plans to update deps/openssl to OpenSSL 3.6 as we'd prefer to stay on Long Term Support (LTS) versions of OpenSSL, we could replace the CI testing against dynamically linked OpenSSL 3.1, which is now out of support, with testing against dynamically linked OpenSSL 3.6 (once all tests pass).

[panva]

we could replace the CI testing against dynamically linked OpenSSL 3.1, which is now out of support, with testing against dynamically linked OpenSSL 3.6 (once all tests pass).

Testing against OpenSSL that's out of support is imho pointless, let's replace 3.1 with 3.6