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 429373

Summary: doesn't handle openswan for IPSEC
Product: Red Hat Enterprise Linux 6 Reporter: Bill Nottingham <notting>
Component: doc-Security_GuideAssignee: Scott Radvan <sradvan>
Status: CLOSED NEXTRELEASE QA Contact: Joshua Wulf <jwulf>
Severity: low Docs Contact:
Priority: low    
Version: 6.0CC: avagarwa, herrold, lcarlon, mhideo, rlandman, rvokal, sgrubb
Target Milestone: rcKeywords: Documentation
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-20 23:35:16 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: 429362, 429371, 547583    
Attachments:
Description Flags
Openswan doc none

Description Bill Nottingham 2008-01-18 22:43:20 UTC
The deployment guide describes ipsec configuration using initscripts ifcfg files
and racoon. If we want to fully switch to openswan, we need to update the
documentation.

This depends on how we decide to handle openswan configuration, though.

Comment 1 Don Domingo 2008-01-21 22:42:33 UTC
setting as NEEDINFO=reporter for content sources.

Comment 3 RHEL Program Management 2009-07-28 21:29:13 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 4 Scott Radvan 2010-02-23 23:50:34 UTC
Marking as NEEDINFO=reporter for content sources if this is to added to the Security Guide.

Comment 5 Bill Nottingham 2010-02-24 17:47:57 UTC
Moving NEEDINFO to openswan maintainer. In any case, the ipsec-tools ifcfg file documentation needs removed, as that's not in RHEL 6.

Comment 6 Avesh Agarwal 2010-02-24 17:59:46 UTC
ipsec-tools are not related to Openswan. So removing ipsec-tools documents should not affect Openswan. And yes if Openswan document is not there then, that should be included in RHEL6 deployment guide.

Comment 7 Douglas Silas 2010-02-28 00:16:02 UTC
I have removed the entire section on IPsec interface configuration from the RHEL6 Deployment Guide. According to Bill: "there is no integration into initscripts or NetworkManager for openswan at this time." That being the case, the likely target for Openswan documentation at this point is the Security Guide (current component).

Comment 8 Scott Radvan 2010-04-15 03:56:08 UTC
happy to write content into the documentation if I can get some advice of the
state of openswan, or some sort of outline/details of what should be covered. anyone?

Comment 9 Bill Nottingham 2010-04-15 13:45:12 UTC
Avesh - can you provide this info?

Comment 10 Avesh Agarwal 2010-04-15 13:59:13 UTC
Sure. I had prepared a document for GSS and QE training last month that I can send to Scott. This doc can be used as a starting point and if something is not clear, I am provide more info.

Comment 11 Scott Radvan 2010-04-16 00:51:26 UTC
Avesh, sounds great, please send asap.

Comment 12 Avesh Agarwal 2010-04-16 13:15:26 UTC
Created attachment 407096 [details]
Openswan doc

Comment 13 Avesh Agarwal 2010-04-16 13:16:30 UTC
Hello Scott,

I have attached the doc, please let me know if you have any questions or need any other details.

Avesh