| Summary: | Protocol ports does not work if hostname is given instead of ipaddress 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: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 6.1 | 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: |
Openswan did not handle protocol and port (leftprotoport) configuration correctly if the hostname parameter was configured instead of the ipaddress parameter using Openswan. This update solves this issue, and Openswan now correctly sets up policies with the correct protocol and port even when the hostname parameter is configured.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-12-06 19:05:21 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 712112 | ||
|
Description
Avesh Agarwal
2011-05-10 13:16:13 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:
Openswan did not handle protocol and port (leftprotoport) configuration correctly if the hostname parameter was configured instead of the ipaddress parameter using Openswan. This update solves this issue, and Openswan now correctly sets up policies with the correct protocol and port even when the hostname parameter is configured.
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 |