You are currently viewing a snapshot of taken on April 21, 2008. Most of this content is highly out of date (some pages haven't been updated since the project began in 1998) and exists for historical purposes only. If there are any pages on this archive site that you think should be added back to, please file a bug.

NSS 3.11.9 Release Notes

31 January 2008




Network Security Services (NSS) 3.11.9 is a patch release for NSS 3.11. The bug fixes in NSS 3.11.9 are described in the "Bugs Fixed" section below.

Distribution Information

The CVS tag for the NSS 3.11.9 release is NSS_3_11_9_RTM.  NSS 3.11.9 requires NSPR 4.7.

See the Documentation section for the build instructions.

NSS 3.11.9 source and binary distributions are also available on for secure HTTPS download:

You also need to download the NSPR 4.7 binary distributions to get the NSPR 4.7 header files and shared libraries, which NSS 3.11.9 requires. NSPR 4.7 binary distributions are in

Bugs Fixed

The following bugs have been fixed in NSS 3.11.9.
  • Bug 353577: Delete dead PURE_STAN code
  • Bug 353714: key search functions ignore the nickname argument
  • Bug 393183: Optstate not freed in ocspclnt.
  • Bug 399304: cert trust lock and refcount lock should not be initialized late
  • Bug 401970: Correct NSS error string for SEC_ERROR_OCSP_RESPONDER_CERT_INVALID
  • Bug 402285: built-in root certs module shows no slot name
  • Bug 403957: nss_InitLock should be replaced with PZ_NewLock in softoken
  • Bug 404610: crashes in strsclnt on NSS_3_11_BRANCH in Stan code
  • Bug 406258: zlib does not compile with new VC2008 compiler (VC9)
  • Bug 411299: Add Identrust


For a list of the primary NSS documentation pages on, see NSS Documentation. New and revised documents available since the release of NSS 3.9 include the following:


NSS 3.11.9 shared libraries are backward compatible with all older NSS 3.x shared libraries. A program linked with older NSS 3.x shared libraries will work with NSS 3.11.9 shared libraries without recompiling or relinking.  Furthermore, applications that restrict their use of NSS APIs to the functions listed in NSS Public Functions will remain compatible with future versions of the NSS shared libraries.


Bugs discovered should be reported by filing a bug report with Bugzilla (product NSS).