This appendix gives detailed information pertaining to the FIPS mode. In particular, the changes to the standard mode and the finite state machine are described. The self-tests required in this mode are described in the appendix on self-tests.
If Libgcrypt is used in FIPS mode, these restrictions are effective:
AES 128 bit symmetric encryption.
AES 192 bit symmetric encryption.
AES 256 bit symmetric encryption.
SHA-1 message digest.
SHA-224 message digest.
SHA-256 message digest.
SHA-384 message digest.
SHA-512 message digest.
SHA3-224 message digest.
SHA3-256 message digest.
SHA3-384 message digest.
SHA3-512 message digest.
HMAC using a SHA-1 message digest.
HMAC using a SHA-224 message digest.
HMAC using a SHA-256 message digest.
HMAC using a SHA-384 message digest.
HMAC using a SHA-512 message digest.
HMAC using a SHA3-224 message digest.
HMAC using a SHA3-256 message digest.
HMAC using a SHA3-384 message digest.
HMAC using a SHA3-512 message digest.
CMAC using a AES key.
RSA encryption and signing.
ECC encryption and signing.
Note that the CRC algorithms are not considered cryptographic algorithms and thus are in addition available.
transient-keyflag for RSA key generation is ignored.
gcry_set_allocation_handlermay not be used. In FIPS mode this function does not have any effect, because FIPS has requirements for memory zeroization.
Note that when we speak about disabling FIPS mode, it merely means
that the function
gcry_fips_mode_active returns false; it does
not mean that any non FIPS algorithms are allowed.
The FIPS mode of Libgcrypt implements a finite state machine (FSM) using 8 states (see Table B.1) and checks at runtime that only valid transitions (see Table B.2) may happen.
States used by the FIPS FSM:
Libgcrypt is not runtime linked to another application. This usually means that the library is not loaded into main memory. This state is documentation only.
Libgcrypt is loaded into memory and API calls may be made. Compiler introduced constructor functions may be run. Note that Libgcrypt does not implement any arbitrary constructor functions to be called by the operating system
The Libgcrypt initialization functions are performed and the library has not yet run any self-test.
Libgcrypt is performing self-tests.
Libgcrypt is in the operational state and all interfaces may be used.
Libgrypt is in the error state. When calling any FIPS relevant
interfaces they either return an error (
or put Libgcrypt into the Fatal-Error state and won’t return.
Libgcrypt is in a non-recoverable error state and will automatically transit into the Shutdown state.
Libgcrypt is about to be terminated and removed from the memory. The application may at this point still run cleanup handlers.
The valid state transitions (see Figure B.1) are:
Power-Off to Power-On is implicitly done by the OS loading Libgcrypt as a shared library and having it linked to an application.
Power-On to Init is triggered by the application calling the
Libgcrypt initialization function
Init to Self-Test is either triggered by a dedicated API call or implicit by invoking a Libgrypt service controlled by the FSM.
Self-Test to Operational is triggered after all self-tests passed successfully.
Operational to Shutdown is an artificial state without any direct action in Libgcrypt. When reaching the Shutdown state the library is deinitialized and can’t return to any other state again.
Shutdown to Power-Off is the process of removing Libgcrypt from the computer’s memory. For obvious reasons the Power-Off state can’t be represented within Libgcrypt and thus this transition is for documentation only.
Operational to Error is triggered if Libgcrypt detected an application error which can’t be returned to the caller but still allows Libgcrypt to properly run. In the Error state all FIPS relevant interfaces return an error code.
Error to Shutdown is similar to the Operational to Shutdown transition (5).
Error to Fatal-Error is triggered if Libgrypt detects an fatal error while already being in Error state.
Fatal-Error to Shutdown is automatically entered by Libgcrypt after having reported the error.
Power-On to Shutdown is an artificial state to document that Libgcrypt has not yet been initialized but the process is about to terminate.
Power-On to Fatal-Error will be triggered if certain Libgcrypt functions are used without having reached the Init state.
Self-Test to Fatal-Error is triggered by severe errors in Libgcrypt while running self-tests.
Self-Test to Error is triggered by a failed self-test.
Operational to Fatal-Error is triggered if Libcrypt encountered a non-recoverable error.
Operational to Self-Test is triggered if the application requested to run the self-tests again.
Error to Self-Test is triggered if the application has requested to run self-tests to get back into operational state after an error.
Init to Error is triggered by errors in the initialization code.
Init to Fatal-Error is triggered by non-recoverable errors in the initialization code.
Error to Error is triggered by errors while already in the Error state.
Libgcrypt does not do any key management on itself; the application
needs to care about it. Keys which are passed to Libgcrypt should be
allocated in secure memory as available with the functions
gcry_calloc_secure. By calling
gcry_free on this memory, the memory and thus the keys are
overwritten with zero bytes before releasing the memory.
For use with the random number generator, Libgcrypt generates 3
internal keys which are stored in the encryption contexts used by the
RNG. These keys are stored in secure memory for the lifetime of the
process. Application are required to use
before process termination. This will zero out the entire secure
memory and thus also the encryption contexts with these keys.