[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <adefb26b-934f-4e13-8d41-d61168744d21@kernel.org>
Date: Sun, 25 Jan 2026 20:46:23 -0700
From: David Ahern <dsahern@...nel.org>
To: Eric Biggers <ebiggers@...nel.org>, netdev@...r.kernel.org
Cc: linux-crypto@...r.kernel.org, Ard Biesheuvel <ardb@...nel.org>,
"Jason A . Donenfeld" <Jason@...c4.com>, Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Simon Horman <horms@...nel.org>
Subject: Re: [PATCH net-next 1/2] ipv6: Switch to higher-level SHA-1 functions
On 1/22/26 10:16 PM, Eric Biggers wrote:
> There's now a proper SHA-1 API that follows the usual conventions for
> hash function APIs: sha1_init(), sha1_update(), sha1_final(), sha1().
> The only remaining user of the older low-level SHA-1 API,
> sha1_init_raw() and sha1_transform(), is ipv6_generate_stable_address().
> I'd like to remove this older API, which is too low-level.
>
> Unfortunately, ipv6_generate_stable_address() does in fact skip the
> SHA-1 finalization for some reason. So the values it computes are not
> standard SHA-1 values, and it sort of does want the low-level API.
>
> Still, it's still possible to use the higher-level functions sha1_init()
> and sha1_update() to get the same result, provided that the resulting
> state is used directly, skipping sha1_final().
>
> So, let's do that instead. This will allow removing the low-level API.
>
> Reviewed-by: Ard Biesheuvel <ardb@...nel.org>
> Signed-off-by: Eric Biggers <ebiggers@...nel.org>
> ---
> net/ipv6/addrconf.c | 21 +++++++++++++--------
> 1 file changed, 13 insertions(+), 8 deletions(-)
>
Acked-by: David Ahern <dsahern@...nel.org>
Powered by blists - more mailing lists