FIPS Design Assurance: Difference between revisions

FIPS Design Assurance (view source)

597 bytes removed , 19 July 2006

canmove, Confirmed users

937

edits

@@ Line 16: / Line 16: @@
 ===Installation===
-NSS releases are available from mozilla.org's FTP site as compressed (gzipped) tar files or zip files. The tar or zip file is expanded into a file system directory in a location that is suitably secured using the capabilities of the local operating system.
+NSS cryptographic module releases are available from mozilla.org's FTP site as compressed (gzipped) tar files or zip files. The tar or zip file is expanded into a directory in a location that is suitably secured using the capabilities of the local operating system.
-Typically, at this point, an application is configured to use NSS libraries from this directory. Such configuration consists of the following steps, which can also be performed with NSS command line utilities.
+Typically, at this point, an application is configured to use NSS cryptographic module libraries from this directory.
-* Initialize the certificate and private key databases.
-* Import the certificates and private keys that are to be used by the application into the databases.
-* Put the NSS cryptographic module into FIPS mode. See [http://wiki.mozilla.org/FIPS_Module_Specification#Approved_Mode_of_Operation Approved Mode of Operation ]  and [http://wiki.mozilla.org/Security_Policy#Specification_of_Security_Policy Security Policy Rule #36] for information on accomplishing this programatically and via command line utilities.
 ===Components===