netdev - Re: [RFC PATCH resend]: Fix output for BEET ipsec

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080326133152.GA3022@gondor.apana.org.au>
Date:	Wed, 26 Mar 2008 21:31:52 +0800
From:	Herbert Xu <herbert@...dor.apana.org.au>
To:	Joakim Koskela <joakim.koskela@...t.fi>
Cc:	netdev@...r.kernel.org, Komu Miika <Miika.Komu@...t.fi>
Subject: Re: [RFC PATCH resend]: Fix output for BEET ipsec

On Wed, Mar 26, 2008 at 11:15:26AM +0200, Joakim Koskela wrote:
> Hi,
> 
> Any comments on this? Would be great to get beet working soon!
> 
> br, j
> 
> == original post:
> 
> This patch fixes the ipsec BEET (Bound End-to-End Tunnel) mode
> interfamily handling of the net-2.6 (25-rc3) kernel, as specified by
> the ietf draft found at:
> 
> http://www.ietf.org/internet-drafts/draft-nikander-esp-beet-mode-08.txt
> 
> It is sent as a RFC as it doesn't fit that neatly into the newly
> cleaned-up xfrm model - I suspect that there could be a better way to
> solve this.
> 
> Signed-off-by: Joakim Koskela <jookos@...il.com>

Thanks for the patch!

In light of the patch I just posted I believe we can drop everything
but the props_header_len adjustments.  Please let me know if it still
doesn't work with my earlier patch.

Cheers,
-- 
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html