From: Tyler Hicks <tyhicks@ou.edu>
To: <netdev@vger.kernel.org>
Cc: <latten@us.ibm.com>, <herbert@gondor.apana.org.au>,
<davem@davemloft.net>
Subject: [IPSEC] RFC 4301 PFP Support
Date: Tue, 11 Dec 2007 13:34:45 -0800 [thread overview]
Message-ID: <20071211213445.GA11887@hestia> (raw)
I'm working on adding populate from packet (PFP) support to the kernel,
as specified in RFC 4301. While testing with openswan (2.4.9), I
noticed that the state selector values in the SAD were empty. It seems
that when openswan sends a ALLOCSPI message, the kernel finds the larval
xfrm_state with selector fields filled in and passes it to openswan.
Openswan will then respond with an UPDSA message that includes an
xfrm_usersa_info that has empty selector values. The kernel assumes
that these selector values are valid and deletes the larval SA and
inserts the new SA containing empty selectors. We need SAs with valid
selectors in the SAD in order to implement PFP support.
Should we just use the larval selectors or should we assume that
openswan will begin to send valid selectors? I asked for the openswan
dev's opinions and they referred me to Herbert Xu. It seems as though
the correct solution would be for openswan to pass valid selectors in
UPDSA messages, even if it is the larval selectors we gave them.
On a side note, Joy Latten has reported to see the same behavior while
using ipsec-tools.
Thanks!
Tyler Hicks
next reply other threads:[~2007-12-11 21:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 21:34 Tyler Hicks [this message]
2007-12-12 1:52 ` [IPSEC] RFC 4301 PFP Support Herbert Xu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071211213445.GA11887@hestia \
--to=tyhicks@ou.edu \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=latten@us.ibm.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).