808bits

SUSE Linux Enterprise Server 12 libgcrypt Cryptographic Module

FIPS 140-2 certificate #2464 · SUSE, LLC · data as of 2026-08-28
Historical. Moved to historical list due to sunsetting. Federal agencies may reference historical validations for existing systems only, not for new procurement.
Caveat: When operated in FIPS mode. The module generates cryptographic keys whose strengths are modified by available entropy

Certificate

Certificate number2464
StandardFIPS 140-2
Statushistorical
Overall level1
Module typeSoftware
EmbodimentMulti-Chip Stand Alone
VendorSUSE, LLC · website
Software versions1.0 [1], 2.0 [2]

Module description

SUSE Libgcrypt is a general purpose cryptographic library based on the code from GnuPG.

Security level exceptions

  • Physical Security: N/A

Approved algorithms

AlgorithmCAVP certificate
AES3433, 3434, 4765, 4766, 4840
DRBG831, 832, 833, 834, 1642, 1643, 1644, 1645, 1646, 1647, 1699
DSA967, 1283, 1297
ECDSA689, 1195, 1237
HMAC2183, 2184, 2185, 2186, 3176, 3177, 3178, 3179, 3241
RSA1757, 2607, 2660
SHS2831, 2832, 2833, 2834, 3908, 3909, 3910, 3911, 3982
Triple-DES1936, 2533, 2551

Other algorithms

NDRNG; RSA (key wrapping; key establishment methodology provides between 112 and 150 bits of encryption strength)

Tested configurations

  • HP Proliant DL320e Gen8 with AES-NI [1]
  • HP Proliant DL320e Gen8 without AES-NI [1]
  • SLES12 operating on FUJITSU Server PRIMERGY CX2570 M2 inside a CX400 M1 enclosure with PAA [2]
  • SLES12 operating on FUJITSU Server PRIMERGY CX2570 M2 inside a CX400 M1 enclosure without PAA [2]
  • SLES12 operating on IBM z13 with PAI [2]
  • SLES12 operating on IBM z13 without PAI [2] (single-user mode)

Validation history

DateTypeLab
2015-10-30Initialatsec information security corporation
2017-11-17Updateatsec information security corporation
2018-01-24Updateatsec information security corporation

Status timeline

As observed by this tracker's snapshots. NIST publishes no dates for list moves; observation began 2026-08-21, so earlier changes carry no date.

  • 2026-08-21: first observed by this tracker, status historical
  • Validation dates on record: 2015-10-30, 2017-11-17, 2018-01-24

Source documents