summaryrefslogtreecommitdiff
path: root/tests/pkcs11/netscape/suites/security/ssl/key3.db
diff options
context:
space:
mode:
authorRobert Relyea <rrelyea@redhat.com>2020-04-14 10:50:06 -0700
committerRobert Relyea <rrelyea@redhat.com>2020-04-14 10:50:06 -0700
commitdc8a52a8c73e0bd35a623a3bb536be4d689e99cc (patch)
treead8f44d8ae7bfaee2212ce476ff5309f29d76da3 /tests/pkcs11/netscape/suites/security/ssl/key3.db
parenta7a61840f766e987cd67100f3835fc3f3da91e9e (diff)
downloadnss-hg-dc8a52a8c73e0bd35a623a3bb536be4d689e99cc.tar.gz
Bug 1629661 MPConfig calls in SSL initializes policy before NSS is initialized. r=mt
NSS has several config functions that multiprocess servers must call before NSS is initialized to set up shared memory caches between the processes. These functions call ssl_init(), which initializes the ssl policy. The ssl policy initialization, however needs to happen after NSS itself is initialized. Doing so before hand causes (in the best case) policy to be ignored by these servers, and crashes (in the worst case). Instead, these cache functions should just initialize those things it needs (that is the NSPR ssl error codes). This patch does: 1) fixes the cache init code to only initialize error codes. 2) fixes the selfserv MP code to 1) be compatible with ssl.sh's selfserv management (at least on Unix), and 2) mimic the way real servers handle the MP_Cache init code (calling NSS_Init after the cache set up). 3) update ssl.sh server policy test to test policy usage on an MP server. This is only done for non-windows like OS's because they can't catch the kill signal to force their children to shutdown. I've verified that the test fails if 2 and 3 are included but 1 is not (and succeeds if all three are included). Differential Revision: https://phabricator.services.mozilla.com/D70948
Diffstat (limited to 'tests/pkcs11/netscape/suites/security/ssl/key3.db')
0 files changed, 0 insertions, 0 deletions