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 1844621 - Backport FIPS keysize fixes from RHEL8 [rhel-7.9.z]
Summary: Backport FIPS keysize fixes from RHEL8 [rhel-7.9.z]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libreswan
Version: 7.9
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Paul Wouters
QA Contact: Ondrej Moriš
URL:
Whiteboard:
Depends On:
Blocks: 1854325
TreeView+ depends on / blocked
 
Reported: 2020-06-05 19:23 UTC by Ravindra Patil
Modified: 2023-10-06 20:27 UTC (History)
7 users (show)

Fixed In Version: 3.25-9.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1854325 (view as bug list)
Environment:
Last Closed: 2020-09-29 21:17:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:4067 0 None None None 2020-09-29 21:17:51 UTC

Description Ravindra Patil 2020-06-05 19:23:13 UTC
Description of problem:

Backport FIPS keysize fixes from RHEL8
- Fix Minimum RSA key size to 2048 (was 3072)
- Fix ECDSA key size check

Version-Release number of selected component (if applicable):
libreswan-3.25-8.1.el7_7.x86_64.rpm

How reproducible:
- RSA keys in FIPS mode needed to be 3072 in libreswan versions < 3.32. 
- For libreswan >= 3.32, FIPS mode will accept 2048 bit keys.
- In non-fips mode, 2048 bit RSA keys are always accepted.

Steps to Reproduce:
1. Key size in FIPS is expected to be 3072 or above. 
2.
3.

Actual results:
# /usr/sbin/ipsec  auto --add con-name
Warning: ignored obsolete keyword 'plutorestartoncrash'
036 FIPS: Rejecting cert with key size 2048 which is under 3072
036 Failed to add connection "con-name" with invalid "left" certificate

Expected results:
Key size less than 3072 like 2048 should be accepted

Additional info:

Comment 8 Ondrej Moriš 2020-06-29 12:32:56 UTC
Before granting qa_acks I need to understand the way this issue is fixed.

1. Fixed libreswan will allow 2048 bit RSA keys in FIPS mode, correct?

2. What is "Fix ECDSA key size check" from the description?

Comment 10 Simo Sorce 2020-06-29 17:11:41 UTC
Requesting Zstream

Comment 11 Simo Sorce 2020-06-29 17:12:24 UTC
Jaroslav, can you run your magic to create the Zstream clones ?

Comment 25 errata-xmlrpc 2020-09-29 21:17:46 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (libreswan bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4067


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