NSSCryptoModuleSpec/Section 10: Design Assurance: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
No edit summary |
||
Line 19: | Line 19: | ||
[http://wiki.mozilla.org/VE_10#VE.10.02.02 VE.10.02.02 ] | [http://wiki.mozilla.org/VE_10#VE.10.02.02 VE.10.02.02 ] | ||
| [http://wiki.mozilla.org/FIPS_Design_Assurance#Configuration_Management Configuration Management] | | [http://wiki.mozilla.org/FIPS_Design_Assurance#Configuration_Management Configuration Management] | ||
Executable files for each platform are listed in [http://wiki.mozilla.org/Security_Policy#Specification_of_Security_Policy Security Policy Rule 36]. | |||
| draft | | draft | ||
|- | |- |
Revision as of 01:11, 11 August 2006
This is a draft document.
Document Description |
DTR Section |
Assessment |
Status |
---|---|---|---|
Configuration Management | Configuration Management
Executable files for each platform are listed in Security Policy Rule 36. |
draft | |
Installation, Initialization, and Start-up | draft | ||
Module Components and Security Policy | Components | draft | |
External Interfaces | N/A. NSS is a software only implementation. It has no external physical ports and interfaces. The external logical interfaces are the API functions. | draft | |
Crypto Officer and User Guidance | Functions | draft |
Return to: NSSCryptoModuleSpec