808bits

SUSE Linux Enterprise Server 12 - OpenSSH Client Module

FIPS 140-2 certificate #2472 · 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 with module SUSE Linux Enterprise Server 12 - OpenSSL Module validated to FIPS 140-2 under Cert. #2435 [1] operating in FIPS mode or with SUSE Linux Enterprise Server OpenSSL Module validated to FIPS 140-2 under Cert. #3038 [2] operating in FIPS mode.

Certificate

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

Module description

SUSE client software that provides encrypted network communication using the SSH protocol.

Security level exceptions

  • Physical Security: N/A
  • Mitigation of Other Attacks: N/A

Approved algorithms

AlgorithmCAVP certificate
CVL483, 1492, 1493

Other algorithms

ChaCha20; Poly1305; UMAC; Curve25519-based ECDH; Ed25519

Tested configurations

  • SUSE Linux Enterprise Server 12 running on HP ProLiant DL320e Gen8 with AES-NI[1]
  • SUSE Linux Enterprise Server 12 running on HP ProLiant DL320e Gen8 without AES-NI[1]
  • SUSE Linux Enterprise Server 12 SP2 running on FUJITSU Server PRIMERGY CX2570 M2 inside a CX400 M1 enclosure with AES-NI[2]
  • SUSE Linux Enterprise Server 12 SP2 running on FUJITSU Server PRIMERGY CX2570 M2 inside a CX400 M1 enclosure without AES-NI[2]
  • SUSE Linux Enterprise Server 12 SP2 running on IBM z13[2] (single-user mode)

Validation history

DateTypeLab
2015-11-13Initialatsec information security corporation
2018-01-02Updateatsec 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-11-13, 2018-01-02

Source documents