netdev - Re: [PATCH] xfrm: Remove inner/outer modes from output path

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] [day] [month] [year] [list]

Message-ID: <ZBGmtKFTYbQJSgEy@gauss3.secunet.de>
Date:   Wed, 15 Mar 2023 12:06:28 +0100
From:   Steffen Klassert <steffen.klassert@...unet.com>
To:     Herbert Xu <herbert@...dor.apana.org.au>
CC:     <netdev@...r.kernel.org>
Subject: Re: [PATCH] xfrm: Remove inner/outer modes from output path

On Fri, Mar 10, 2023 at 05:40:32PM +0800, Herbert Xu wrote:
> The inner/outer modes were added to abstract out common code that
> were once duplicated between IPv4 and IPv6.  As time went on the
> abstractions have been removed and we are now left with empty
> shells that only contain duplicate information.  These can be
> removed one-by-one as the same information is already present
> elsewhere in the xfrm_state object.
> 
> Just like the input-side, removing this from the output code
> makes it possible to use transport-mode SAs underneath an
> inter-family tunnel mode SA.
> 
> Signed-off-by: Herbert Xu <herbert@...dor.apana.org.au>

Also applied to ipsec-next, thanks a lot!