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.
Created attachment 744240[details]
patch for crl loading order
Description of problem:
When pluto makes an attempt to load the CRLs from /etc/ipsec.d/crls on startup, loading always fails since it checks to see if the CRL has a loaded CA. Since load_crls comes before load_authcerts_from_nss in plutomain.c, there won't be any CA certs available.
Version-Release number of selected component (if applicable):
openswan-2.6.32-19.el6_3
How reproducible:
1. Load CA cert into NSSdb, place crl file into /etc/ipsec.d/crls
2. Start pluto with debug logging: 'service ipsec start'
In the logs you will see the loading of the CRL and the failure:
Changing to directory '/etc/ipsec.d/crls'
loaded crl file 'crl.crl' (1747 bytes)
| file content is not binary ASN.1
| -----BEGIN X509 CRL-----
| -----END X509 CRL-----
| file coded in PEM format
...
crl issuer cacert not found for (file:///etc/ipsec.d/crls/crl.crl)
(The file:/// is just the printed path, while wrong for linux, this path was not attempted at all)
At this point ipsec auto --listall does not show any crl. Issuing an ipsec auto --rereadall will then load the CRL properly since the CA has been loaded beforehand.
Additional info:
Attaching a patch that swaps the order of the loading functions in plutomain.c. My testing with this shows that now the CRL's load properly on initial startup.
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.
http://rhn.redhat.com/errata/RHBA-2013-1718.html
Created attachment 744240 [details] patch for crl loading order Description of problem: When pluto makes an attempt to load the CRLs from /etc/ipsec.d/crls on startup, loading always fails since it checks to see if the CRL has a loaded CA. Since load_crls comes before load_authcerts_from_nss in plutomain.c, there won't be any CA certs available. Version-Release number of selected component (if applicable): openswan-2.6.32-19.el6_3 How reproducible: 1. Load CA cert into NSSdb, place crl file into /etc/ipsec.d/crls 2. Start pluto with debug logging: 'service ipsec start' In the logs you will see the loading of the CRL and the failure: Changing to directory '/etc/ipsec.d/crls' loaded crl file 'crl.crl' (1747 bytes) | file content is not binary ASN.1 | -----BEGIN X509 CRL----- | -----END X509 CRL----- | file coded in PEM format ... crl issuer cacert not found for (file:///etc/ipsec.d/crls/crl.crl) (The file:/// is just the printed path, while wrong for linux, this path was not attempted at all) At this point ipsec auto --listall does not show any crl. Issuing an ipsec auto --rereadall will then load the CRL properly since the CA has been loaded beforehand. Additional info: Attaching a patch that swaps the order of the loading functions in plutomain.c. My testing with this shows that now the CRL's load properly on initial startup.