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 814958[details]
Output of 'ipsec barf'
Description of problem:
When 384 or 512 bit SHA2 IKE encryption/authentication algorithm is used, pluto keeps aborting on responder machine. With 256 bit SHA2 it works fine.
Version-Release number of selected component (if applicable):
openswan-2.6.32-27.el6
How reproducible:
100%
Steps to Reproduce:
1. Setup initiator and responder as follows (ipsec.conf):
version 2.0
config setup
plutodebug="lifecycle"
protostack=netkey
nat_traversal=yes
virtual_private=
oe=off
conn test
authby=secret
type=transport
left=<initiator>
right=<responder
ike=aes128-sha2_512 # (or sha2_384)
esp=3des-sha1
ikev2=insist
auto=add
2. Start ipsec on both initiator and responder (service ipsec start)
3. Initiate connection from initiator (ipsec auto --up test)
4. See /var/log/messages on responder.
Actual results:
Connection does not work.
Responder (/var/log/messages):
002 added connection description "test"
ipsec__plutorun: /usr/libexec/ipsec/_plutorun: line 250: 19521 Aborted (core dumped) /usr/libexec/ipsec/pluto --nofork --secretsfile /etc/ipsec.secrets --ipsecdir /etc/ipsec.d --debug-lifecycle --use-netkey --uniqueids --nat_traversal --virtual_private oe=off
ipsec__plutorun: !pluto failure!: exited with error status 134 (signal 6)
ipsec__plutorun: restarting IPsec after pause...
...
(and repeating)
Expected results:
Connection successful.
Additional info:
This is *not* a regression in 6.5 from 6.4, in happens in openswan-2.6.32-21.el6_4 as well. In FIPS mode it does not work as well. Output of 'ipsec barf' from responder is attached.
May be I am just not configuring it correctly, where can I find the list of suitable options for ike=? Man page ipsec.conf(5) says: "...The options must be suitable as a value of ipsec_spi(8)´s --ike option.", but there is not ike option mentioned in ipsec_spi(8).
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-2014-1588.html
Created attachment 814958 [details] Output of 'ipsec barf' Description of problem: When 384 or 512 bit SHA2 IKE encryption/authentication algorithm is used, pluto keeps aborting on responder machine. With 256 bit SHA2 it works fine. Version-Release number of selected component (if applicable): openswan-2.6.32-27.el6 How reproducible: 100% Steps to Reproduce: 1. Setup initiator and responder as follows (ipsec.conf): version 2.0 config setup plutodebug="lifecycle" protostack=netkey nat_traversal=yes virtual_private= oe=off conn test authby=secret type=transport left=<initiator> right=<responder ike=aes128-sha2_512 # (or sha2_384) esp=3des-sha1 ikev2=insist auto=add 2. Start ipsec on both initiator and responder (service ipsec start) 3. Initiate connection from initiator (ipsec auto --up test) 4. See /var/log/messages on responder. Actual results: Connection does not work. Responder (/var/log/messages): 002 added connection description "test" ipsec__plutorun: /usr/libexec/ipsec/_plutorun: line 250: 19521 Aborted (core dumped) /usr/libexec/ipsec/pluto --nofork --secretsfile /etc/ipsec.secrets --ipsecdir /etc/ipsec.d --debug-lifecycle --use-netkey --uniqueids --nat_traversal --virtual_private oe=off ipsec__plutorun: !pluto failure!: exited with error status 134 (signal 6) ipsec__plutorun: restarting IPsec after pause... ... (and repeating) Expected results: Connection successful. Additional info: This is *not* a regression in 6.5 from 6.4, in happens in openswan-2.6.32-21.el6_4 as well. In FIPS mode it does not work as well. Output of 'ipsec barf' from responder is attached.