Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1664521

Summary: libreswan 3.25 in FIPS mode is incorrectly rejecting X.509 public keys that are >= 3072 bits
Product: Red Hat Enterprise Linux 7 Reporter: Paul Wouters <pwouters>
Component: libreswanAssignee: Paul Wouters <pwouters>
Status: CLOSED CURRENTRELEASE QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: urgent Docs Contact: Mirek Jahoda <mjahoda>
Priority: urgent    
Version: 7.6CC: jaster, mjahoda, mthacker, omoris, salmy
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: libreswan-3.25-4.1.el7_6 Doc Type: Bug Fix
Doc Text:
While running in FIPS mode, Libreswan incorrectly checked the length of X.509 public keys as if it is in bytes. Consequently, 3072-bit keys were incorrectly detected as 384-bit and rejected. With this update, the check has been fixed to count with bits instead of bytes, and the keys are no longer incorrectly rejected in the described scenario.
Story Points: ---
Clone Of:
: 1664522 1665369 (view as bug list) Environment:
Last Closed: 2019-08-08 13:04:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1664522, 1665369    

Description Paul Wouters 2019-01-09 04:09:46 UTC
In libreswan 3.25 a check was added if running in FIPS mode to ensure X.509 public keys are at least 3072 bits . Unfortunately, the value it checks is in bytes, so it incorrectly rejects 3072 bit keys, thinking these are 384 bit keys.

upstream patch: https://github.com/libreswan/libreswan/commit/61d076456774c1eda85921dfdfd6d4c520a4dd89

Comment 3 Ondrej Moriš 2019-01-09 11:50:45 UTC
I think this is an urgent issue from FIPS perspective. Even though package will not be re-validated. This effectively blocks using public keys in FIPS mode in libreswan.

Comment 4 Ondrej Moriš 2019-01-09 11:53:27 UTC
Adding qa_ack+. Paul can you please confirm #3? If it is correct then I think this is definitely z-stream material (we have 7.6.2 errata in progress right now).