A. Restrictions in FIPS mode

If Libgcrypt is used in FIPS mode these restrictions are effective:

• The cryptographic algorithms are restricted to this list:

  GCRY_CIPHER_3DES

  3 key EDE Triple-DES symmetric encryption.

  GCRY_CIPHER_AES128

  AES 128 bit symmetric encryption.

  GCRY_CIPHER_AES192

  AES 192 bit symmetric encryption.

  GCRY_CIPHER_AES256

  AES 256 bit symmetric encryption.

  GCRY_MD_SHA1

  SHA-1 message digest.

  GCRY_MD_SHA224

  SHA-224 message digest.

  GCRY_MD_SHA256

  SHA-256 message digest.

  GCRY_MD_SHA384

  SHA-384 message digest.

  GCRY_MD_SHA512

  SHA-512 message digest.

  GCRY_MD_SHA1,GCRY_MD_FLAG_HMAC

  HMAC using a SHA-1 message digest.

  GCRY_MD_SHA224,GCRY_MD_FLAG_HMAC

  HMAC using a SHA-224 message digest.

  GCRY_MD_SHA256,GCRY_MD_FLAG_HMAC

  HMAC using a SHA-256 message digest.

  GCRY_MD_SHA384,GCRY_MD_FLAG_HMAC

  HMAC using a SHA-384 message digest.

  GCRY_MD_SHA512,GCRY_MD_FLAG_HMAC

  HMAC using a SHA-512 message digest.

  GCRY_PK_RSA

  RSA encryption and signing.

  GCRY_PK_DSA

  DSA signing.

  Note that the CRC algorithms are not considered cryptographic algorithms and thus are in addition available.

• RSA and DSA key generation refuses to create a key with a keysize of less than 1024 bits.
• The transient-key flag for RSA key generation is ignored.
• Support for the VIA Padlock engine is disabled.
• FIPS mode may only be used on systems with a /dev/random device. Switching into FIPS mode on other systems will fail at runtime.
• Saving and loading a random seed file is not ignored.
• An X9.31 style random number generator is used in place of the large-pool-CSPRNG generator.
• The Alternative Public Key Interface (gcry_ac_xxx) is not supported and all API calls return an error.
• Registration of external modules is not supported.
• Message digest debugging is disabled.
• All debug output related to cryptographic data is suppressed.
• On-the-fly self-tests are not performed, instead of this self-tests are run before entering operational state.
• The function gcry_set_allocation_handler may not be used. If it is used Libgcrypt will enter the error state.
• A handler set by gcry_set_outofcore_handler is ignored.
• A handler set by gcry_set_fatalerror_handler is ignored.