canmove, Confirmed users
937
edits
FIPSFSM: Difference between revisions
Jump to navigation
Jump to search
→Finite State Model
(→States) |
|||
| Line 2: | Line 2: | ||
==Finite State Model== | ==Finite State Model== | ||
The NSS FIPS cryptographic module runs as part of an application program on a host computer. When a running program makes an NSS library initialization call, the state changes and power-up self-tests are performed. See [http://wiki.mozilla.org/Section_9:_Self_Tests Self Tests] for a description of the power-up self-tests. If the self-tests succeed, the NSS library is considered initialized and the module enters the normal operational state | The NSS FIPS cryptographic module runs as part of an application program on a host computer. When a running program makes an NSS library initialization call, the state changes and power-up self-tests are performed. See [http://wiki.mozilla.org/Section_9:_Self_Tests Self Tests] for a description of the power-up self-tests. If the self-tests succeed, the NSS library is considered initialized and the module enters the normal operational state. Refer to the tables below when studying this state transition diagram.<br> | ||
[[ Image:Fsmm2.png ]] | [[ Image:Fsmm2.png ]] | ||
If the module ever enters the error state, the NSS library needs to be shut down (transition 3.0) and reinitialized (transition 1.1). | |||
The action of the finite state model as a result of all other combinations of data and control inputs is to return an appropriate error code (e.g., CKR_HOST_MEMORY, CKR_TOKEN_WRITE_PROTECTED, CKR_TEMPLATE_INCOMPLETE, , or CKR_ATTRIBUTE_VALUE_INVALID) and go back to the current state. | |||
==States== | ==States== | ||