office-gobmx/external/nss
..
asan.patch.1
clang-cl.patch.0
ExternalPackage_nss.mk
ExternalProject_nss.mk
macos-dlopen.patch.0
Makefile
Module_nss.mk
nsinstall.py
nss-android.patch.1
nss-bz1646594.patch.1
nss-ios.patch
nss-restore-manual-pre-dependencies.patch.1
nss-win32-make.patch.1
nss.bzmozilla1238154.patch
nss.cygwin64.in32bit.patch
nss.nowerror.patch
nss.patch
nss.utf8bom.patch.1
nss.vs2015.patch
nss.vs2015.pdb.patch
nss.windows.patch
nss_macosx.patch
README
ubsan.patch.0
UnpackedTarball_nss.mk
Wincompatible-function-pointer-types.patch.0

Contains the Network Security Services (NSS) libraries from Mozilla

== Fips 140 and signed libraries ==

Fips 140 mode is not supported. That is, the *.chk files containing the
checksums for the cryptographic module are not delivered into instdir and will
not be part of the OOo installation sets.

Signing has been turned off because
- we change the rpath (install names)  after signing which breaks the signatures
(Mac)
- sqlite conflicts with the system sqlite when signing which breaks the build

See also
[https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/NSS_Tech_Notes/nss_tech_note6]

== libsqlite3 ==

With all supported macOS SDK we use
NSS_USE_SYSTEM_SQLITE=1
to build using the system sqlite.

== system NSS on Linux ==

Note that different Linux distributions use different SONAMEs for the
NSS libraries, so it is not possible to use --with-system-nss and build
a portable generic LO installation set, despite NSS upstream apparently
maintaining ABI compatibility.

Debian Squeeze:
0x000000000000000e (SONAME)             Library soname: [libnss3.so.1d]
Fedora 20:
0x000000000000000e (SONAME)             Library soname: [libnss3.so]

For the record, the LSB specified SONAME is libnss3.so
http://refspecs.linuxfoundation.org/LSB_4.1.0/LSB-Core-generic/LSB-Core-generic/libnss3.html