[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8b27d067-d401-88b9-f784-4589b27f8e32@nohats.ca>
Date: Wed, 10 Apr 2024 09:52:36 -0400 (EDT)
From: Paul Wouters <paul@...ats.ca>
To: Sabrina Dubroca <sd@...asysnail.net>
cc: Nicolas Dichtel <nicolas.dichtel@...nd.com>, antony.antony@...unet.com,
Steffen Klassert <steffen.klassert@...unet.com>,
Herbert Xu <herbert@...dor.apana.org.au>, netdev@...r.kernel.org,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>, devel@...ux-ipsec.org,
Leon Romanovsky <leon@...nel.org>, Eyal Birger <eyal.birger@...il.com>
Subject: Re: [devel-ipsec] [PATCH ipsec-next v9] xfrm: Add Direction to the
SA in or out
On Wed, 10 Apr 2024, Sabrina Dubroca via Devel wrote:
> 2024-04-10, 10:37:27 +0200, Nicolas Dichtel wrote:
>> Le 10/04/2024 à 10:17, Sabrina Dubroca a écrit :
>> [snip]
>> >> Why isn't it possible to restrict the use of an input SA to the input path and
>> >> output SA to xmit path?
>> >
>> > Because nobody has written a patch for it yet :)
>> >
>> For me, it should be done in this patch/series ;-)
>
> Sounds good to me.
If this is not the case currently, what happens when our own generated
SPI clashes with a peer generated SPI? Could it be we end up using the
wrong SA state?
Paul
Powered by blists - more mailing lists