Rocky Linux 8 and 9 libgcrypt Cryptographic Module

Certificate

Approved Algorithms (46)

Security Levels (Table 1)

Derived Review-Risk Graph (review prompts, not findings)

flowchart LR
  %% Deterministic review-risk graph for Rocky Linux 8 and 9 libgcrypt Cryptographic Module
  %% Review prompts and evidence gaps, NOT vulnerability findings.
  subgraph CMVP["CMVP-disclosed clues"]
    C2["[low] Firmware update / recovery<br/>/ rollback (referenced in<br/>text)<br/><i>update<br/>Recovery</i>"]
    C3["[high] Unauthenticated /<br/>self-test / status service<br/>surface<br/><i>Symmetric encryption<br/>Symmetric decryption<br/>Symmetric encryption with AES-XTS (for data storage)</i>"]
    C5["[low] Protocol / secure-channel<br/>references (may be KDF<br/>names, not a live channel)<br/><i>HTTPS<br/>no library/version identified</i>"]
    C6["[low] Operating system / runtime<br/>referenced (boundary<br/>membership not asserted)<br/><i>operating system<br/>linux<br/>kernel</i>"]
  end
  subgraph Inference["Derived inference"]
    I2["Possible only, trusted<br/>code is reachable through<br/>update and recovery paths."]
    I3["Some services may process<br/>input before, or without,<br/>operator authentication."]
    I5["Possible only, a protocol<br/>is referenced, but whether<br/>it is a live channel or<br/>only a KDF/algorithm name<br/>is unconfirmed."]
    I6["Possible only, a<br/>runtime/OS is referenced,<br/>but its membership in the<br/>cryptographic boundary is<br/>not established."]
  end
  subgraph Risk["Reviewer question"]
    R2["Are update images<br/>authenticated before<br/>parsing, and are<br/>downgrade/rollback paths<br/>constrained?"]
    R3["Can unauthenticated<br/>services leak state,<br/>consume resources, or<br/>transition security state?"]
    R5["If a live TLS/SSH/IKE<br/>channel exists, could<br/>library CVEs apply, or is<br/>this only a<br/>KDF/documentation name?"]
    R6["If the OS/runtime is<br/>in-boundary, could its<br/>CVEs be hidden by<br/>firmware-only versioning?"]
  end
  subgraph Evidence["Evidence needed to close"]
    E2["confirm the disclosure<br/>itself (keyword hit,<br/>context unverified) ·<br/>update image format ·<br/>signature-before-parse<br/>proof · anti-rollback /<br/>downgrade policy"]
    E3["pre-auth reachability<br/>matrix · rate limits and<br/>output redaction ·<br/>abuse-case tests"]
    E5["confirm the disclosure<br/>itself (keyword hit,<br/>context unverified) ·<br/>library identity and<br/>version ·<br/>certificate-validation<br/>behaviour · protocol-CVE<br/>disposition"]
    E6["confirm the disclosure<br/>itself (keyword hit,<br/>context unverified) ·<br/>runtime identity and<br/>config · kernel/runtime<br/>hardening profile ·<br/>patch/backport manifest"]
  end
  C2 --> I2 --> R2 --> E2
  C3 --> I3 --> R3 --> E3
  C5 --> I5 --> R5 --> E5
  C6 --> I6 --> R6 --> E6
  classDef clue fill:#eef3f9,stroke:#6f7f91,color:#1f3a5f;
  classDef infer fill:#fff7e6,stroke:#b98500,color:#6b4e00;
  classDef risk fill:#fbe9e9,stroke:#b02a2a,color:#7a1f1f;
  classDef evidence fill:#e6f4ea,stroke:#1e7d34,color:#14532d;
  class C2,C3,C5,C6 clue;
  class I2,I3,I5,I6 infer;
  class R2,R3,R5,R6 risk;
  class E2,E3,E5,E6 evidence;

flowchart LR
  %% Deterministic clue tier for Rocky Linux 8 and 9 libgcrypt Cryptographic Module
  %% confidence: high = structured record field; medium = structured but soft; low (dashed) = bare keyword hit, context unverified
  subgraph CMVP["CMVP-disclosed clues (deterministic)"]
    C2["[low] Firmware update / recovery / rollback (referenced in text)<br/><i>update<br/>Recovery</i><br/>src: text:keyword"]
    C3["[high] Unauthenticated / self-test / status service surface<br/><i>Symmetric encryption<br/>Symmetric decryption<br/>Symmetric encryption with AES-XTS (for data storage)</i><br/>src: securityPolicy.services"]
    C5["[low] Protocol / secure-channel references (may be KDF names, not a live channel)<br/><i>HTTPS<br/>no library/version identified</i><br/>src: text:keyword"]
    C6["[low] Operating system / runtime referenced (boundary membership not asserted)<br/><i>operating system<br/>linux<br/>kernel</i><br/>src: text:keyword"]
  end
  classDef clueHigh fill:#eef3f9,stroke:#2f6fb0,stroke-width:2px,color:#1f3a5f;
  classDef clueMedium fill:#eef3f9,stroke:#6f7f91,color:#1f3a5f;
  classDef clueLow fill:#f7f7f7,stroke:#999,stroke-dasharray:4 4,color:#444;
  class C2,C5,C6 clueLow;
  class C3 clueHigh;

Security Policy, page by page

Ctrl IQ, Inc. Rocky Linux 8 and 9 libgcrypt Cryptographic Module Prepared by: atsec information security corporation

Austin, TX 78759 Document version: 1.1 www.atsec.com Last update: 2025-12-18

Rocky Linux 8 and 9 libgcrypt Cryptographic Module © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module Table of Contents 2.10 © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module List of Tables List of Figures © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module

This document is the non-proprietary FIPS 140-3 Security Policy for version rocky8.20240929 and rocky9.20240929 of the Rocky Linux 8 and 9 libgcrypt Cryptographic Module. It contains the security rules under which the module must operate and describes how this module meets the requirements as specified in FIPS PUB 140-3 (Federal Information Processing Standards Publication 140-3) for an overall Security Level 1

This Security Policy describes the features and design of the module named Rocky Linux 8 and 9 libgcrypt Cryptographic Module using the terminology contained in the FIPS 140-3 specification. The FIPS 140-3 Security Requirements for Cryptographic Module specifies the security requirements that will be satisfied by a cryptographic module utilized within a security system protecting sensitive but unclassified information. The NIST/CCCS Cryptographic Module Validation Program (CMVP) validates cryptographic module to FIPS 140-3. Validated products are accepted by the Federal agencies of both the USA and Canada for the protection of sensitive or designated information. including this notice. Other documentation is proprietary to their authors. In preparing the Security Policy document, the laboratory formatted the vendor-supplied documentation for consolidation without altering the technical statements therein contained. The further refining of the Security Policy document was conducted iteratively throughout the conformance testing, wherein the Security Policy © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module was submitted to the vendor, who would then edit, modify, and add technical contents. The vendor would also supply additional documentation, which the laboratory formatted into the existing Security Policy, and resubmitted to the vendor for their final editing. © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module

Purpose and Use: The Rocky Linux 8 and 9 libgcrypt Cryptographic Module (hereafter referred to as “the module”) is a software library implementing general purpose cryptographic algorithms. The module provides cryptographic services to applications running in the user space of the underlying operating system through an application program interface (API). Module Type: Software Module Embodiment: MultiChipStand Cryptographic Boundary: The module consists of the shared library file (i.e. libgcrypt.so.20) which constitutes the cryptographic boundary. The block diagram in Figure 1 shows the cryptographic boundary of the module, its interfaces with the operational environment and the flow of information between the module and operator. The block diagram is representative of both versions rocky8.20240929 and rocky9.20240929 of the cryptographic module. Tested Operational Environment’s Physical Perimeter (TOEPP): The TOEPP is the general-purpose computer on which the module is installed. The entropy source and the PAA provided by the processor are located within the module’s physical perimeter and outside of the module’s cryptographic boundary. Figure 1: Block Diagram © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module

Tested Module Identification

• Hardware: N/A for this module. Tested Module Identification
• Software, Firmware, Hybrid (Executable Code Sets): N/A N/A Table 2: Tested Module Identification
• Software, Firmware, Hybrid (Executable Code Sets) Tested Module Identification
• Hybrid Disjoint Hardware: N/A for this module. Tested Operational Environments - Software, Firmware, Hybrid: N/A N/A N/A N/A Table 3: Tested Operational Environments - Software, Firmware, Hybrid Vendor-Affirmed Operational Environments - Software, Firmware, Hybrid: N/A for this module.

The module does not claim any excluded components.

Modes List and Description: © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module Nonapproved NonApproved Table 4: Modes List and Description Mode Change Instructions and Status: When the module starts up successfully, after passing all the pre-operational self-test and the cryptographic algorithms self-tests (CASTs), the module is operating in the approved mode of operation by default and can only be transitioned into the non-approved mode by calling one of the non-approved services listed in the NonApproved Services table. The module will transition back to approved mode when approved service is called. Section 4 provides details on the service indicator implemented by the module. The service indicator identifies

Approved Algorithms: © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module Table 5: Approved Algorithms The above table lists all approved cryptographic algorithms of the module, including specific key lengths employed for approved services, and implemented modes or methods of operation of the algorithms. Vendor-Affirmed Algorithms: N/A Table 6: Vendor-Affirmed Algorithms Non-Approved, Allowed Algorithms: N/A for this module. Non-Approved, Allowed Algorithms with No Security Claimed: N/A for this module. Non-Approved, Not Allowed Algorithms: © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module Table 7: Non-Approved, Not Allowed Algorithms The table above lists all non-approved cryptographic algorithms of the module employed by the non-approved services.

© 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module () AsymKeyPairKeyGen © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module AsymKeyPairKeyVer AsymKeyPairKeyGen () © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module Table 8: Security Function Implementations

AES XTS The length of a single data unit encrypted with the XTS-AES shall not exceed 2²⁰ AES blocks, that is 16MB of data. To meet the requirement stated in IG C.I, the module implements a check that ensures, before performing any cryptographic operation, that the two AES keys used in AES XTS mode are not identical. The AES-XTS mode shall only be used for the cryptographic protection of data on storage devices. The AESXTS shall not be used for other purposes, such as the encryption of data in transit. Key_1 and Key_2 shall be generated and/or established independently according to the rules for component symmetric keys from NIST SP 800-133r2, Section 6.3. The module provides password-based key derivation (PBKDF), compliant with SP800-132. The module supports option 1a from Section 5.4 of [SP800-132], in which the Master Key (MK) or a segment of it is used directly as the Data Protection Key (DPK). In accordance with [SP800-132] and FIPS 140-3 IG D.N, the following requirements shall be met.

• Derived keys shall only be used in storage applications. The Master Key (MK) shall not be used for other purposes. The module accepts length of the MK or DPK of 112 bits or more. © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module

• A portion of the salt, with a length of at least 128 bits, shall be generated randomly using the SP80090A DRBG.
• The iteration count shall be selected as large as possible, as long as the time required to generate the key using the entered password is acceptable for the users. The minimum value accepted by the module is 1000.
• Passwords or passphrases, used as an input for the PBKDF, shall not be used as cryptographic keys.
• The minimum length of the password or passphrase accepted by the module is 8 characters. The probability of guessing the value, assuming a worst-case scenario of all digits, is estimated to be at most 10-8. Combined with the minimum iteration count as described below, this provides an acceptable trade-off between user experience and security against brute-force attacks. The calling application shall also observe the rest of the requirements and recommendations specified in [SP800-132]. Authenticated encryption and decryption The module does not establish SSPs using an approved key transport scheme (KTS). However, it does offer approved authenticated algorithms that can be used by an external operator/application as part of an approved KTS. SHA-1 Use SHA-1 is only approved when used in approved modes for message digest and HMAC. The use of SHA-1 is non approved in any other case. Specifically, the use of SHA-1 for digital signature generation (e.g., ECSDA and RSA) or verification is non-approved.

Table 9: Entropy Certificates NonPhysical Table 10: Entropy Sources The Module provides an SP800-90A-compliant Deterministic Random Bit Generator (DRBG) for creation of key components of asymmetric keys, and random number generation. The seeding (and automatic reseeding) of the DRBG is done with get_random(). The module supports the Hash_DRBG, HMAC_DRBG and CTR_DRBG. The DRBG is initialized during module initialization; the module loads by default the DRBG using the HMAC_DRBG mechanism with SHA-256 and © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module without prediction resistance. A different DRBG mechanism can be chosen by invoking the gcry_control(GCRYCTL_DRBG_REINIT) function. The module uses an [SP800-90B]-compliant entropy source specified in the above table. This entropy source is located within the module’s physical perimeter but outside of the module’s cryptographic boundary. The module obtains 384 bits to seed the DRBG and 256 bits to reseed it, respectively corresponding to 384 bits of entropy for seeding and 256 bits for reseeding, which is full entropy. Outputs of multiple GetEntropy() calls are concatenated to receive the entropy input length greater than 256 bits. The output is truncated to get the entropy input string which is not a multiple of 256. The module performs the DRBG health tests as defined in Section 11.3 of [SP800-90A]. The module complies with the Public Use Document for ESV certificate E210 by reading entropy data from the get_random() function with the GRND_RANDOM flag set, which corresponds to the GetEntropy() conceptual interface. The operational environment on the ESV certificate is identical to the operating system described in this document. There are no maintenance requirements for the entropy source.

The module provides an [SP800-90Arev1]-compliant Deterministic Random Bit Generator (DRBG) for the creation of key components of asymmetric keys, and random number generation. The Cryptographic Key Generation (CKG) methods implemented in the module for Approved services in approved mode are compliant with section 5.1 of [SP800-133rev2] and with IG D.H. For generating RSA and ECDSA keys the module implements asymmetric key generation services compliant with [FIPS186-5]. A seed (i.e., the random value) used in asymmetric key generation is directly obtained from the [SP800-90Arev1] DRBG. Intermediate key generation values are not output from the module and are explicitly zeroized after processing the service. 2.10 Key Establishment The module does not provide any key establisment mechanism.

The module does not implement industry protocols, therefore this section is not applicable. © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module

N/A N/A N/A N/A Table 11: Ports and Interfaces As a software-only module, the module does not have physical ports. The operator can only interact with the module through the API provided by the module. Thus, the physical ports are interpreted to be the physical ports of the hardware platform on which the module runs. The logical interfaces are logically separated from each other by the API design. All data output via data output interface is inhibited when the module is performing pre-operational test or zeroization or when the module enters error state. The module does not implement a control output interface. © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module

Table 12: Roles No support is provided for multiple concurrent operators.

t W,E W,E W,E W,E © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module with AESCMAC W,E W,E,Z G,W,E W,E,Z G,E,Z © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module G,W,E G G G W,E,Z G,E,Z G,W,E G - Modulegenerated - Modulegenerated © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module W,E W,E G - Modulegenerated G,R - Modulegenerated G,R W,E © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module W,E W,E G W,E W,E W,E W,E © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module Perform ondemand e e N/A N/A G W,E W,E W,E W,E W,E W,E © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module N/A N/A N/A N/A N/A N/A N/A N/A Table 13: Approved Services The table above lists the approved services. For each service, the table lists the associated cryptographic algorithm(s), the role to perform the service, the cryptographic keys or CSPs involved, and their access type(s). The following convention is used to specify access rights to a CSP:

• G = Generate: The module generates or derives the SSP.
• R = Read: The SSP is read from the module (e.g., the SSP is output).
• W = Write: The SSP is updated, imported, or written to the module.
• E = Execute: The module uses the SSP in performing a cryptographic operation.
• Z = Zeroise: The module zeroises the SSP. The details of the approved cryptographic algorithms including the CAVP certificate numbers can be found in the Approved Algorithm table. © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module Table 14: Non-Approved Services

The module does not have the capability of loading software or firmware from an external source. © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module

The integrity of the module is verified comparing the HMAC-SHA-256 value calculated at run time with the HMAC-SHA-256 value embedded in the module’s ELF header that was computed at build time for each software component of the module. If the HMAC values do not match, the test fails and the module enters the error state.

Integrity tests are performed as part of the Pre-Operational Self-Tests. The module provides the Self-Test service to perform self-tests on demand which includes the pre-operational tests (i.e., integrity test) and cryptographic algorithm self-tests (CASTs). This service can be invoked relying on the gcry_control(GCRYCTL_SELFTEST) API function call or by powering-off and reloading the module. During the execution of the on-demand self-tests, services are not available, and no data output or input is possible. In order to verify whether the self-tests have succeeded and the module is in the Operational state, the calling application may invoke the gcry_control(GCRYCTL_OPERATIONAL_P). The function will return TRUE if the module is in the operational state, FALSE if the module is in the Error state. © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module

Type of Operational Environment: Modifiable How Requirements are Satisfied: The module operates in a modifiable operational environment per FIPS 140-3 level 1 specification: the module executes on a general-purpose operating system, which allows modification, loading, and execution of software that is not part of the validated module. If properly installed, the operating system provides process isolation and memory protection mechanisms that ensure appropriate separation for memory access among the processes on the system. Each process has control over its own data and uncontrolled access to the data of other processes is prevented.

The module shall be installed as stated in section 11. Instrumentation tools like the ptrace system call, gdb and strace, userspace live patching, as well as other tracing mechanisms offered by the Linux environment such as ftrace or systemtap, shall not be used in the operational environment. The use of any of these tools implies that the cryptographic module is running in a non-validated operational environment. © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module

The module is comprised of software only and therefore this section is not applicable. © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module

This module does not implement any non-invasive security mechanism, and therefore this Section is not applicable. © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module

Table 15: Storage Areas zeroization function calls. Table 16: SSP Input-Output Methods form within the physical perimeter of the operational environment. This is allowed by [FIPS140-3_IG] 9.5.A, according to the “CM Software to/from App via TOEPP Path” entry on the Key Establishment Table. © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module N/A Table 17: SSP Zeroization Methods The memory occupied by SSPs is allocated by regular memory allocation operating system calls. The application that is acting as the CO is responsible for calling the appropriate zeroization functions provided in the module's API and listed in the above table. Calling gcry_free(), which will zeroize the SSPs and also invoke the corresponding API functions listed in the above table to zeroize SSPs. The zeroization functions overwrite the operating system call. © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module with AESCMAC 112524288 Modulegenerated RSA

P-224, P256, P384, P521 - 112, P-224, P256, P384, P521 - 112, Modulegenerated Modulegenerated © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module P-224, P256, P384, P521 - 112, P-224, P256, P384, P521 - 112, - N/A © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module D.L D.L G G G © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module D.L D.L G G Table 18: SSP Table 1 Modulegenerated RSA Modulegenerated RSA © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module Modulegenerated Modulegenerated © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module Table 19: SSP Table 2 The tables above summarizes the Sensitive Security Parameters (SSPs) that are used by the cryptographic services implemented in the module.

The SHA-1 algorithm as implemented by the module will be non-approved for all purposes, starting January 1, 2031. © 2025 Ctrl IQ, Inc., atsec information security.

HMACSHA2-256 HMACSHA2-256 Table 20: Pre-Operational Self-Tests The module performs pre-operational self-tests automatically when the module is becoming available for the consuming application. Pre-operational self-tests ensure that the module is not corrupted. While the module is executing the pre-operational self-tests, services are not available, input and output are inhibited. The module is not available for use by the calling application until the pre-operational self-tests are completed successfully.

© 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module © 2025 Ctrl IQ, Inc., atsec information security.

Rocky Linux 8 and 9 libgcrypt Cryptographic Module © 2025 Ctrl IQ, Inc., atsec information security.