Name Date Size #Lines LOC

..01-May-2024-

prj/H18-Oct-2019-

makefile.mkH A D11-Mar-20244.4 KiB16695

nss.patchH A D20-Dec-20228.2 KiB210190

nss.patch.mingwH A D18-Oct-20195.2 KiB144133

nss_freebsd.patchH A D29-Jan-2022449 1612

nss_linux.patchH A D29-Jan-2022718 1514

nss_macosx.patchH A D29-Jan-2022878 1716

nss_sizes.patchH A D04-Apr-20229.3 KiB277270

nss_win.patchH A D29-Jan-2022101.5 KiB2,9532,832

readme.txtH A D20-Jan-20243 KiB7559

readme.txt

1Relation between nss, moz, moz_prebuilt
2---------------------------------------
3nss contains the security libraries which are also part of moz. However nss is
4meant to be more current, that is, it to be updated more often. This
5should be easier than updating moz.
6
7When nss is build, it depends on an environment variable (ENABLE_NSS_MODULE)
8which is by default set to YES. In this case nss is build before moz. The nss
9libraries/lib files/headers built in moz are then not delivered. Otherwise they
10would overwrite those from nss. The nss libraries build in moz are then
11removed from mozruntime.zip (build in moz/solver/bin), they are removed from the
12lib directory (for example moz/unxlngi6.pro/lib), and the nss and nspr headers
13are also removed (inc/nss and inc/nspr).  The nss libraries from the nss module
14are then added to mozruntime.zip.
15
16This also applies for moz_prebuilt. Therefore moz and moz_prebuilt must be build
17again after changes have been made to the libraries in the nss module.
18
19Also when moz was updated to use a newer version of mozilla, then one must make
20sure that new files which also belong to nss are not delivered and are removed
21from mozruntime.zip.
22
23Fips 140 and signed libraries
24-------------------------------
25Fips 140 mode is not supported. That is, the *.chk files containing the
26checksums for the cryptographic module are not delivered into solver and will
27not be part of the OOo installation sets.
28
29Signing has been turned off because
30- we change the rpath (install names) after signing which breaks the signatures
31(Mac)
32- sqlite conflicts with the system sqlite when signing which breaks the build
33
34
35libfreebl3
36----------
37Porting to other platforms may require to deliver other variants of
38libfreebl*. The library name varies according to the platform. Changes need to
39be made to
40ooo/moz/extractfiles.mk
41ooo/moz/zipped/makefile.mk
42sun/moz_prebuilt/zipped/makefile.mk
43
44See also
45http://www.mozilla.org/projects/security/pki/nss/tech-notes/tn6.html
46
47
48Windows builds of nss
49---------------------
50To build nss on Windows you need the MozillaBuild tools.
51
52Wiki page containing the link to the build tools:
53https://wiki.mozilla.org/MozillaBuild#Overview
54
55The direct link (latest supported version):
56https://ftp.mozilla.org/pub/mozilla/libraries/win32/MozillaBuildSetup-3.4.exe
57
58libsqlite3
59----------
60The problem described here was found on Mac with OS 10.6
61NSS cannot use the system sqlite on Mac because the base line is still MacOS
6210.4. That system sqlite is incompatible with the softokn3 in nss which requires
63a later version of sqlite.
64When we used a more current Mac SDK then we could set
65NSS_USE_SYSTEM_SQLITE=1
66to build using the system sqlite.
67
68We cannot deliver sqlite in the lib directory of the solver. This directory is
69used by tools of the build environment. Using the sqlite from NSS breaks the
70tools if they use system libraries which are linked with the system
71sqlite. Therefore we deliver it into lib/sqlite on unix systems.
72
73See also issue
74http://qa.openoffice.org/issues/show_bug.cgi?id=106132
75