This NSS documentation was just imported from our legacy MDN repository. It currently is very deprecated and likely incorrect or broken in many places.
Network Security Services (NSS) is a set of libraries designed to support cross-platform development of communications applications that support TLS, S/MIME, and other Internet security standards. For a general overview of NSS and the standards it supports, see mozilla_projects_nss_overview.
Windows and Unix use different naming conventions for static and dynamic libraries:
In addition, Windows has “import” libraries that bind to dynamic libraries. So the NSS library has the following forms:
libnss3.so- Linux shared library
libnss3.dylib- MacOS shared library
libnss3.sl- HP-UX shared library
libnss.a- Unix static library
nss3.dll- Windows shared library
nss3.lib- Windows import library binding to
nss.lib- Windows static library
NSS, SSL, and S/MIME have all of the above forms.
The following static libraries aren’t included in any shared libraries
crmf.libprovides an API for CRMF operations.
jar.libprovides an API for creating JAR files.
The following static libraries are included only in external loadable PKCS #11 modules:
nssckfw.libprovides an API for writing PKCS #11 modules.
swfci.libprovides support for software FORTEZZA.
The following shared libraries are standalone loadable modules, not meant to be linked with directly:
fort32.dllprovides support for hardware FORTEZZA.
swft32.dllprovides support for software FORTEZZA.
nssckbi.dlldefines the default set of trusted root certificates.