On Thu, Apr 21, 2011 at 1:06 PM, Bernhard Thalmayr <bernhard.thalm...@painstakingminds.com> wrote: > Hi experts, according to > 'https://developer.mozilla.org/en/NSS_reference/NSS_environment_variables' > PKCS#11 crypto module will throw an error if not initialized by the process > which will use it (even it has been initialized by the parent process).
I guess you're referring to the NSS_STRICT_NOFORK environment variable. > It seems this behaviour has been changed with NSS 3.12.9 or > (3.12.8,3.12.7,3.12.6) as I don't get an error using NSS 3.12.9 but NSS > 3.12.5. > > I've read all available release notes but could not find a hint when and why > this has changed. > > So the question arises ...do I have to change the way of initializing NSS or > not? In the bugs fixed in NSS 3.12.6 - 3.12.9: https://bugzilla.mozilla.org/buglist.cgi?resolution=FIXED&classification=Components&query_format=advanced&product=NSS&target_milestone=3.12.6&target_milestone=3.12.7&target_milestone=3.12.8&target_milestone=3.12.9 I believe this bug, fixed in NSS 3.12.9, causes the change you observed: https://bugzilla.mozilla.org/show_bug.cgi?id=610843 It seems that you need to call the new SECMOD_RestartModules function in the child process. Wan-Teh -- dev-tech-crypto mailing list dev-tech-crypto@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-crypto
