mirror of
https://github.com/nodejs/node.git
synced 2025-05-19 22:10:53 +00:00
87719d792b
This commit makes node load extra certificates at startup instead of first use. PR-URL: https://github.com/nodejs/node/pull/23354 Fixes: https://github.com/nodejs/node/issues/20434 Refs: https://github.com/nodejs/node/issues/20432 Reviewed-By: Sam Roberts <vieuxtech@gmail.com> Reviewed-By: Sakthipriyan Vairamani <thechargingvolcano@gmail.com> Reviewed-By: Refael Ackermann <refack@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net>
23 lines
700 B
JavaScript
23 lines
700 B
JavaScript
'use strict';
|
|
const common = require('../common');
|
|
const fixtures = require('../common/fixtures');
|
|
const assert = require('assert');
|
|
const { fork } = require('child_process');
|
|
|
|
// This test ensures that trying to load extra certs won't throw even when
|
|
// there is no crypto support, i.e., built with "./configure --without-ssl".
|
|
if (process.argv[2] === 'child') {
|
|
// exit
|
|
} else {
|
|
const NODE_EXTRA_CA_CERTS = fixtures.path('keys', 'ca1-cert.pem');
|
|
|
|
fork(
|
|
__filename,
|
|
['child'],
|
|
{ env: Object.assign({}, process.env, { NODE_EXTRA_CA_CERTS }) },
|
|
).on('exit', common.mustCall(function(status) {
|
|
// client did not succeed in connecting
|
|
assert.strictEqual(status, 0);
|
|
}));
|
|
}
|