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.
libreswan has exactly the same behaviour as openswan. I tested it in rhel7 and I used libreswan-3.8-5.el7.
+++ This bug was initially created as a clone of Bug #730975 +++
Description of problem:
Openswan doesn't work with ike=modp1536 option, which is suggested as one of examples in manual pages of ipsec.conf.
Version-Release number of selected component (if applicable):
openswan-2.6.32-4.el6_1.1
How reproducible:
always
Steps to Reproduce:
1.cp ipsec.conf /etc/ipsec.conf
version 2.0
config setup
protostack=netkey
nat_traversal=yes
plutostderrlog=/var/log/pluto.log
conn testA
auto=add
authby=secret
type=transport
left=127.0.0.1
right=127.0.0.1
ike=modp1536
phase2=esp
phase2alg=aes-sha1
loopback=yes
2.cp ipsec.secrets /etc/ipsec.secrets
: PSK "whatever"
3.ip xfrm state flush
4.service ipsec restart
5.ipsec auto --up testA
6.ip xfrm state
Actual results of ipsec auto --up testA:
000 initiating all conns with alias='testA'
021 no connection named "testA"
Expected results:
Succesfully create an IPsec connection
Additional info:
I have checked output of tcpdump, packets are unencrypted.
--- Additional comment from Jaroslav Aster on 2014-06-05 07:48:32 EDT ---
Hi,
I can confirm it and then I did some tests and found out that there is something wrong in parsing ike option. A lot of more things do not work and end with same error.
example:
1, all alone dh
ike=modp1536 # fail
ike=dh22 # fail
ike=dh23 # fail
ike=dh24 # fail
...
2, all alone hash
ike=md5 # fail
ike=sha1 # fail
3, mix dh and hash
ike=md5;dh22 # fail
ike=sha1;modp1024 # fail
...
4,
ike=aes-md5;dh22,modp1024 # fail
Man pages says that it should be possible to set these values, ike=modp1536 is as an example in man page ipsec.conf.
It seems only values from right can miss.
ike=aes-md5;dh22,3des # pass
ike=aes-md5,3des # pass
ike=aes,3des # pass
Hi Paul,
I can still see it in man page ipsec.conf in the latest libreswan's build for rhel7. So, it is not fixed.
# rpm -q libreswan
libreswan-3.12-1.el7.x86_64
# man ipsec.conf | col -b | grep 'ike=modp1536'
ike=aes128-sha1;dh22, ike=3des-md5;modp1024,aes-sha1;modp1536 or ike=modp1536. The options must be suitable as a value of ipsec_spi(8)'s --ike option. The default is to
It seemed to have appeared in two places :/
I just fixed the ipsec.conf ike.xml files upstream and regenerated the man page, so it will be correct in 3.13.
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