From: David Miller <davem@davemloft.net>
To: herbert@gondor.apana.org.au
Cc: martin@strongswan.org, linux-crypto@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH 0/3] xfrm: ESP Traffic Flow Confidentiality padding (v3)
Date: Fri, 10 Dec 2010 14:44:22 -0800 (PST) [thread overview]
Message-ID: <20101210.144422.52203130.davem@davemloft.net> (raw)
In-Reply-To: <20101209124732.GA28931@gondor.apana.org.au>
From: Herbert Xu <herbert@gondor.apana.org.au>
Date: Thu, 9 Dec 2010 20:47:32 +0800
> On Wed, Dec 08, 2010 at 03:37:48PM +0100, Martin Willi wrote:
>> The following patchset adds Traffic Flow Confidentiality padding. The
>> first patch introduces a new Netlink XFRM attribute to configure TFC via
>> userspace. Patch two and three implement the padding logic in IPv4 and
>> IPv6 ESP. Padding is always done using the RFC4303 format an is clamped
>> to the PMTU.
>>
>> Changes from v2:
>> - Remove unused flag field in attribute, use a plain u32 as attribute payload
>> - Reject installation of TFC padding on non-tunnel SAs
>
> Looks good to me. Thanks for the hard work Martin!
>
> Acked-by: Herbert Xu <herbert@gondor.apana.org.au>
All applied, thanks everyone!
prev parent reply other threads:[~2010-12-10 22:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 14:37 [PATCH 0/3] xfrm: ESP Traffic Flow Confidentiality padding (v3) Martin Willi
2010-12-08 14:37 ` [PATCH 1/3] xfrm: Add Traffic Flow Confidentiality padding XFRM attribute Martin Willi
2010-12-08 14:37 ` [PATCH 2/3] xfrm: Traffic Flow Confidentiality for IPv4 ESP Martin Willi
2010-12-08 14:37 ` [PATCH 3/3] xfrm: Traffic Flow Confidentiality for IPv6 ESP Martin Willi
2010-12-09 12:47 ` [PATCH 0/3] xfrm: ESP Traffic Flow Confidentiality padding (v3) Herbert Xu
2010-12-10 22:44 ` David Miller [this message]
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=20101210.144422.52203130.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=martin@strongswan.org \
--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).