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 1070356 - openswan breaks NAT-T draft clients (and possibly ike fragmentation)
Summary: openswan breaks NAT-T draft clients (and possibly ike fragmentation)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: openswan
Version: 6.5
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: rc
: ---
Assignee: Paul Wouters
QA Contact: Aleš Mareček
URL:
Whiteboard:
: 1072922 (view as bug list)
Depends On:
Blocks: 1070358 1090273
TreeView+ depends on / blocked
 
Reported: 2014-02-26 16:35 UTC by Paul Wouters
Modified: 2018-12-05 17:27 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1070358 (view as bug list)
Environment:
Last Closed: 2014-10-14 08:19:19 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
patch for NAT-T draft payloads (6.22 KB, patch)
2014-02-26 16:35 UTC, Paul Wouters 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1588 0 normal SHIPPED_LIVE openswan bug fix and enhancement update 2014-10-14 01:39:53 UTC

Description Paul Wouters 2014-02-26 16:35:52 UTC 
Created attachment 868101 [details]
patch for NAT-T draft payloads

Description of problem:

When a client supporting only non-RFC versions of NAT-T connect to openswan, the connection is rejected with:

 ***parse ISAKMP Key Exchange Payload:
|    next payload type: ISAKMP_NEXT_NONCE
|    length: 260
| got payload 0x400(ISAKMP_NEXT_NONCE) needed: 0x400 opt: 0x102080
"any--east-l2tp"[1] 192.1.2.254 #1: next payload type of ISAKMP Nonce Payload has an unknown value: 130
"any--east-l2tp"[1] 192.1.2.254 #1: malformed payload in packet
| payload malformed after IV
| 
"any--east-l2tp"[1] 192.1.2.254 #1: sending notification PAYLOAD_MALFORMED to 192.1.2.254:500

Version-Release number of selected component (if applicable):
2.6.32-27.2

This can be tested most easily using Windows XP, as it does not support the NAT-T in RFC version, only draft version 2.

the cause is due to bug introduced while backporting the CVE fix for libreswan to openswan. A change in the payload_names struct accidentally left out the private use payload names (which include the two draft NAT-T payloads and the IKE fragmentation payload)

Patch attached to this bug,
Comment 4 Paul Wouters 2014-04-09 14:41:24 UTC 
For this scenario, you need a setup that has an "old" client behind NAT to openswan as a server.

We have added an option ikev1_natt={bofh|rfc|draft} to libreswan that can suppress sending the RFC value, so that newer clients also fall into the older code that is broken in the latest openswan build, but this option hasn't made it into a release yet. I can make a patch that would apply to openswan so you can build it and configure it so that it does not understand the rfc but only the draft.

Otherwise, the easiest way to test this now is to use a Windows XP VM, as it does not support the RFC method, only the draft method.

I don't know how this customer is but Matt Rogers should know.
Comment 7 Karel Srot 2014-04-19 10:59:21 UTC 
Hi Paul,
is this a duplicate to bug 1070356? If yes, could you please close this one?
Comment 8 Paul Wouters 2014-04-19 16:09:40 UTC 
(In reply to Karel Srot from comment #7)
> Hi Paul,
> is this a duplicate to bug 1070356? If yes, could you please close this one?

uhm, you are asking if 1070356 is a duplicate of 1070356 ?

I'm a software engineer, not a philosopher :)
Comment 9 Paul Wouters 2014-04-23 00:46:26 UTC 
note that bz#1072922 is a duplicate of this bug
Comment 10 Paul Wouters 2014-04-23 01:04:49 UTC 
*** Bug 1072922 has been marked as a duplicate of this bug. ***
Comment 17 errata-xmlrpc 2014-10-14 08:19:19 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
Note You need to log in before you can comment on or make changes to this bug.