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 1018327

Summary: ipsec.conf man page lacks example for AES-GCM configuration
Product: Red Hat Enterprise Linux 6 Reporter: Alicja Kario <hkario>
Component: openswanAssignee: Paul Wouters <pwouters>
Status: CLOSED ERRATA QA Contact: Aleš Mareček <amarecek>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.5CC: amarecek, arubin, eparis
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1162770 (view as bug list) Environment:
Last Closed: 2014-10-14 08:18:54 UTC Type: Bug
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: 1162770    
Attachments:
Description Flags
replacement phase2alg.xml none

Description Alicja Kario 2013-10-11 17:28:02 UTC
Description of problem:
The encryption configuration with AES-GCM is not described in ipsec.conf man page

Version-Release number of selected component (if applicable):
openswan-2.6.32-25.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. man ipsec.conf | col -b | grep aes_gcm

Actual results:
*nothing found*

Expected results:
example with valid phase2 algorithms, e.g.:
phase2alg=aes_gcm_a-224-null


Additional info:

Comment 1 RHEL Program Management 2013-10-15 01:34:02 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 3 Paul Wouters 2014-02-14 04:15:04 UTC
Attached the updated phase2alg.xml file. This can be replace the openswan version on the next openswan update we do. Sorry we missed it on this one.

Comment 4 Paul Wouters 2014-02-14 04:15:40 UTC
Created attachment 863088 [details]
replacement phase2alg.xml

replacement phase2alg.xml

Comment 5 Alicja Kario 2014-02-14 10:27:09 UTC
(In reply to Paul Wouters from comment #4)
> Created attachment 863088 [details]
> replacement phase2alg.xml
> 
> replacement phase2alg.xml

Looks good.

One extra thing, since it's in the same section of man page. Would it be possible to list the available DH group sizes explicitly?
While RFC5114  does list some parameters, it doesn't say which is which (e.g. doesn't say that the dh1 is 768bit, dh2 is 1024, etc.). Higher group sizes like 1536 bit or 2048 bit are even harder to find...

Comment 6 Alicja Kario 2014-02-14 10:30:34 UTC
spelling:

> adding the salt size to the key size. Therefor, to interop with an older

s/Therefor/Therefore/

it probably should also be interoperate, not interop

> are necessarilly supported here.</para>

s/necessarilly/necessarily/

Comment 10 errata-xmlrpc 2014-10-14 08:18:54 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-2014-1588.html