[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0a51d41e-124e-479e-afd7-50246e3b0520@6wind.com>
Date: Wed, 10 Apr 2024 08:32:20 +0200
From: Nicolas Dichtel <nicolas.dichtel@...nd.com>
To: antony.antony@...unet.com, Steffen Klassert
<steffen.klassert@...unet.com>, Herbert Xu <herbert@...dor.apana.org.au>,
netdev@...r.kernel.org
Cc: "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>,
Sabrina Dubroca <sd@...asysnail.net>
Subject: Re: [PATCH ipsec-next v9] xfrm: Add Direction to the SA in or out
Le 09/04/2024 à 19:56, Antony Antony a écrit :
> This patch introduces the 'dir' attribute, 'in' or 'out', to the
> xfrm_state, SA, enhancing usability by delineating the scope of values
> based on direction. An input SA will now exclusively encompass values
> pertinent to input, effectively segregating them from output-related
> values. This change aims to streamline the configuration process and
> improve the overall clarity of SA attributes.
>
> This feature sets the groundwork for future patches, including
> the upcoming IP-TFS patch.
>
> Signed-off-by: Antony Antony <antony.antony@...unet.com>
> ---
> v8->v9:
> - add validation XFRM_STATE_ICMP not allowed on OUT SA.
>
> v7->v8:
> - add extra validation check on replay window and seq
> - XFRM_MSG_UPDSA old and new SA should match "dir"
>
> v6->v7:
> - add replay-window check non-esn 0 and ESN 1.
> - remove :XFRMA_SA_DIR only allowed with HW OFFLOAD
Why? I still think that having an 'input' SA used in the output path is wrong
and confusing.
Please, don't drop this check.
Regards,
Nicolas
Powered by blists - more mailing lists