RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2070550 - Change FIPS module version to include hash of specfile, patches and sources
Summary: Change FIPS module version to include hash of specfile, patches and sources
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: openssl
Version: 9.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Clemens Lang
QA Contact: Stanislav Zidek
Depends On:
Blocks: 2082585
TreeView+ depends on / blocked
Reported: 2022-03-31 12:26 UTC by Clemens Lang
Modified: 2023-06-05 16:06 UTC (History)
2 users (show)

Fixed In Version: openssl-3.0.1-29.el9
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 2082585 (view as bug list)
Last Closed: 2023-06-05 16:06:43 UTC
Type: Bug
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CRYPTO-2475 0 None None None 2022-03-31 12:26:37 UTC
Red Hat Issue Tracker CRYPTO-7006 0 None None None 2022-03-31 12:35:59 UTC
Red Hat Issue Tracker RHELPLAN-117512 0 None None None 2022-03-31 12:36:04 UTC

Description Clemens Lang 2022-03-31 12:26:38 UTC
Description of problem:
The FIPS module version should uniquely identify a build that we do, so that we can be sure which specific binary is being submitted for validation and was certified.

At the moment, OpenSSL uses %{version}-%(date +%Y-%m-%d), which brings some risks w.r.t. build server timezone and differing build time on different architectures.

The gnutls and libgcrypt specfiles came up with a nice solution for the problem that uses a hash over the specfile, all source files, and all patches. Since our infrastructure will never rebuild a package with the same NVR, a modification to the specfile is necessary to get a new build, and the FIPS module version will automatically change due to that.

We should change to the method used by gnutls and libgcrypt, see https://gitlab.com/redhat/centos-stream/rpms/gnutls/-/blob/c9s/gnutls.spec#L1-13 and https://gitlab.com/redhat/centos-stream/rpms/libgcrypt/-/blob/c9s/libgcrypt.spec#L1-14.

Version-Release number of selected component (if applicable):

How reproducible:
Use openssl list -providers to list the FIPS module version

Steps to Reproduce:
1. ft 9.0 + redhat.crypto.fips + ssh
2. openssl list -providers | grep -A1 FIPS

Actual results:
    name: Red Hat Enterprise Linux 9 - OpenSSL FIPS Provider
    version: 3.0.1-20220318

Expected results:
    name: Red Hat Enterprise Linux 9 - OpenSSL FIPS Provider
    version: 3.0.1-[a-f0-9]{16}

Comment 7 Clemens Lang 2023-06-05 16:06:43 UTC
RHEL 9.1 contains openssl-3.0.1-43.el9_0.

Note You need to log in before you can comment on or make changes to this bug.