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 1145231 - libreswan 3.10 upgrade breaks old ipsec.secrets configs
Summary: libreswan 3.10 upgrade breaks old ipsec.secrets configs
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libreswan
Version: 7.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Paul Wouters
QA Contact: Aleš Mareček
URL:
Whiteboard:
Depends On: 1144941
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-22 15:18 UTC by Paul Wouters
Modified: 2015-03-05 10:22 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1144941
Environment:
Last Closed: 2015-03-05 10:22:49 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0431 0 normal SHIPPED_LIVE libreswan bug fix and enhancement update 2015-03-05 14:52:35 UTC

Description Paul Wouters 2014-09-22 15:18:27 UTC
+++ This bug was initially created as a clone of Bug #1144941 +++

libreswan-3.8 and before used to have this in README.nss:

"""
Add following to /etc/ipsec.secrets file:
: RSA "name of certificate in nss db" ""
"""

but libreswan 3.10 no longer accepts ipsec.secrets lines with a passphrase in them, breaking old configuration after an upgrade:

"""
Sep 22 08:46:51 oslt pluto[15307]: "/etc/ipsec.d/fs.secrets" line 1: RSA private key file -- unexpected token after friendly_name
[...]
Sep 22 08:46:52 oslt pluto[15307]: "FS" #1: I am sending my cert
Sep 22 08:46:52 oslt pluto[15307]: "FS" #1: I am sending a certificate request
Sep 22 08:46:52 oslt pluto[15307]: "FS" #1: unable to locate my private key for RSA Signature
"""

It's easy enough to fix this by editing the ipsec secrets file once it's clear what the problem is, but it took me a while to figure out that libreswan had been upgraded on my system and it had changed its secret-file format.

It would be nice if libreswan would accept the old type secret-lines and maybe just issue a warning about the ignored passphrase field.

Version-Release number of selected component (if applicable):
libreswan-3.10-3.fc20.x86_64

Comment 6 errata-xmlrpc 2015-03-05 10:22:49 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, 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://rhn.redhat.com/errata/RHBA-2015-0431.html


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