Changes

3. The third exception is applications that must have a separately managed environment. Typically these applications would have a mode (probably default) which would open NSS normally, but could be configured to use their own NSS environment. The options to use the system or private environment should not be hard coded in the application, but should be under user/administrator control. Applications of this class would include Server products or test modes of application products (like Firefox profiles). In this mode the application should initialize NSS with it's traditional Init call, passing in the appropriate private database.

On linuxLinux, the effect of the above initialization will be to:

1)#Open a database in the home directory of the user running. With the flags specified by the application (probably ~/.pki/nssdb).2)#Load any User specified PKCS #11 modules.3)#Open the system database in /etc/pki/nssdb readonly.4)#Load any System specified PKCS #11 modules.5)#Load the nss NSS builtins module.

How this happens will be explained later. First , but first we discuss where the requirements for the above come from.