Allowed algorithms: Diffie-Hellman (key agreement key establishment methodology provides 112 bits of encryption strength) EC Diffie-Hellman (CVL Cert. Validated to FIPS 140-2 Consolidated Validation Certificate Security Policy It provides a simple C language application programming interface to access the secure communications protocols as well as APIs to parse and write X.509, PCKS#12, and other required structures which is shipped with Red Hat Enterprise Linux 7.4." "GnuTLS is a secure communications library implementing the TLS and DTLS protocols. #1307 and #1309, key agreement key establishment methodology provides between 128 and 256 bits of encryption strength) RSA (key wrapping key establishment methodology provides between 112 and 256 bits of encryption strength) MD5 NDRNG #1307 and #1309 key agreement key establishment methodology provides between 112 and 256 bits of encryption strength) EC Diffie-Hellman (CVL Certs. Allowed algorithms: Diffie-Hellman (CVL Certs. Red Hat Enterprise Linux 7.4 running on Dell PowerEdge R630 without PAA (single-user mode) Tested Configuration(s): Red Hat Enterprise Linux 7.4 running on Dell PowerEdge R630 with PAA Validated to FIPS 140-2 Consolidated Validation Certificate Security Policy Vendor Product Link The module generates cryptographic keys whose strengths are modified by available entropy) Red Hat Enterprise Linux GnuTLS Cryptographic Module Please contact the CMVP if any errors are discovered or comments with suggestions for improvement of the validation listings. NOTE3: All questions regarding the implementation and/or use of any module located on the CMVP module validation lists should first be directed to the appropriate vendor point-of-contact (listed for each entry). NOTE2: The operator of a cryptographic module is responsible for ensuring that the algorithms and key lengths are in compliance with the requirements of NIST SP 800-131A. The algorithms, protocols, and cryptographic functions listed as "Other" or "Allowed" have not been tested through the CMVP and are not FIPS-Approved. Additionally, the descriptions may not necessarily reflect the capabilities of the modules when operated in the FIPS-Approved mode. The descriptions do not imply endorsement by the U.S. NOTE1: Module descriptions are provided by the module vendors and have not been verified for accuracy by the CMVP. If the module is embedded in a product or application, ask the product or application vendor to provide a signed letter or statement affirming that the unmodified validated cryptographic module is integrated in the solution the module provides all the cryptographic services in the solution and provide reference to the modules validation certificate number from this listing. VPN, SmartCard, USB memory token, etc.) or the module is embedded in a larger product or application (e.g. When selecting a module from a vendor, verify that the module is either the product or application itself (e.g. In addition, other vendors, who are not found in this list, may incorporate a validated cryptographic module from this list embedded into their own products. There may be a larger number of security products or applications available which use an embedded validated cryptographic module, than the number of modules which are found in this list. If the cryptographic module is a component of a larger product or application, one should contact the product or application vendor in order to determine how the product utilizes the embedded validated cryptographic module. A module may either be an embedded component of a product or application, or a complete product in-and-of-itself. It is important to note that the items on this list are cryptographic modules.