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.

Description of problem:
NSS IPsec profile uses an interpretation of RFC 4945 that causes regression for those CA deployments that set the critical flags on key usage payloads.

Using the TLS profile of NSS, which was in use before using the NSS IPsec profile, does not reject based on critical flags.


Proposed fix:
Verify certificates using the IPsec profile first, if that fails, try using the TLS profile. (The TLS profile method tries as TLS server, then as TLS client).

By chaining the new method with the old method, we ensure there is no regression for those using the old method and those needing the new method.

See related rhbz#1643388

Proposed patch from upstream: https://github.com/libreswan/libreswan/commit/7de7d5cdb6717101b8161891ed4344dfd32f5e4c

This was tested against upstream test case https://github.com/libreswan/libreswan/tree/master/testing/pluto/ikev2-x509-02-eku to show no regression on EKU.

note the certificates with the bogus critical flag were created by tinyca. Apparently when you change any setting and save it, it sets the critical flag. So when you go to set server certificate settings and save them, client certificate settings switch to critical, despite not touching client certificate settings at all.

This also probably means it is fairly uncommon as tinyca is not widely used.

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, 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/RHSA-2019:3391