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.

Bug 704548

Summary:	AH protocol broken with Openswan
Product:	Red Hat Enterprise Linux 6	Reporter:	Avesh Agarwal <avagarwa>
Component:	openswan	Assignee:	Avesh Agarwal <avagarwa>
Status:	CLOSED ERRATA	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	medium	Docs Contact:
Priority:	urgent
Version:	6.2	CC:	amarecek, ebenes, iboverma, jwest, sgrubb
Target Milestone:	rc	Keywords:	Reopened, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openswan-2.6.32-5.el6	Doc Type:	Bug Fix
Doc Text:	Previously, Openswan failed to set up AH (Authentication Header) mode security associations (SAs). This was because Openswan was erroneously processing the AH mode as if it was the ESP (Ecrypted Secure Payload) mode, and was expecting an encryption key. This update fixes this issue, and it is now possible to properly set up AH mode SAs.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-12-06 19:05:28 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	712168

Description Avesh Agarwal 2011-05-13 14:50:33 UTC

Description of problem:
AH protocol negotiation does not work with Openswan, and SAs are not setup.


Version-Release number of selected component (if applicable):
2.6.32-4.el6

How reproducible:
Always

Steps to Reproduce:
1. Configure
phase2=ah
phase2alg=sha1

2. Negotiate a connection.
3. Connection negotiation is not complete.
  
Actual results:
SAs are not setup.

Expected results:
SAs should be setup.

Additional info:

Comment 7 Martin Prpič 2011-07-13 19:42:43 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Previously, Openswan failed to set up AH (Authentication Header) mode security associations (SAs). This was because Openswan was erroneously processing the AH mode as if it was the ESP (Ecrypted Secure Payload) mode, and was expecting an encryption key. This update fixes this issue, and it is now possible to properly set up AH mode SAs.

Comment 11 errata-xmlrpc 2011-12-06 19:05:28 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.

http://rhn.redhat.com/errata/RHBA-2011-1761.html