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
| ||
|
Message-ID: <20190821065911.GO2879@gauss3.secunet.de> Date: Wed, 21 Aug 2019 08:59:11 +0200 From: Steffen Klassert <steffen.klassert@...unet.com> To: Sabrina Dubroca <sd@...asysnail.net> CC: <netdev@...r.kernel.org>, Herbert Xu <herbert@...dor.apana.org.au> Subject: Re: [PATCH RFC ipsec-next 0/7] ipsec: add TCP encapsulation support (RFC 8229) On Fri, Aug 16, 2019 at 04:18:14PM +0200, Sabrina Dubroca wrote: > Hi Steffen, > > 2019-06-25, 12:11:33 +0200, Sabrina Dubroca wrote: > > This patchset introduces support for TCP encapsulation of IKE and ESP > > messages, as defined by RFC 8229 [0]. It is an evolution of what > > Herbert Xu proposed in January 2018 [1] that addresses the main > > criticism against it, by not interfering with the TCP implementation > > at all. The networking stack now has infrastructure for this: TCP ULPs > > and Stream Parsers. > > Have you had a chance to look at this? I was going to rebase and > resend, but the patches still apply to ipsec-next and net-next (patch > 2 is already in net-next as commit bd95e678e0f6). I had a look and I have no general objection against this. If you think the patchset is ready for inclusion, just remove the RFC and resend it. I'll have a closer on it look then.
Powered by blists - more mailing lists