[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250310165857.3584612-1-nstange@suse.de>
Date: Mon, 10 Mar 2025 17:58:53 +0100
From: Nicolai Stange <nstange@...e.de>
To: "David S. Miller" <davem@...emloft.net>,
David Ahern <dsahern@...nel.org>
Cc: Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Simon Horman <horms@...nel.org>,
netdev@...r.kernel.org,
linux-kernel@...r.kernel.org,
Nicolai Stange <nstange@...e.de>
Subject: [PATCH v1 0/4] ipv6: sr: make SR HMAC __init continue on missing algos
Hi all,
this series prepares for prohibiting any SHA1 usage when booting in FIPS
mode -- SHA1 will be sunset by NIST by the end of 2030 ([1]) and then at
latest, attempts to instantiate it will have to be made to fail with
-ENOENT (in FIPS mode only). Note that distros might want to make this
move downstream today already.
The problem is that the SR HMAC __init, and thus the IPv6 subsys as a whole,
fails to come up upon encountering such an error.
This series makes it to continue upon ENOENTs from the hmac instantiations.
Thanks!
Nicolai
[1] https://www.nist.gov/news-events/news/2022/12/nist-retires-sha-1-cryptographic-algorithm
Nicolai Stange (4):
ipv6: sr: reject unsupported SR HMAC algos with -ENOENT
ipv6: sr: factor seg6_hmac_exit()'s per-algo code into separate
function
ipv6: sr: factor seg6_hmac_init_algo()'s per-algo code into separate
function
ipv6: sr: continue initialization at ENOENT HMAC instantiation
failures
net/ipv6/seg6_hmac.c | 141 +++++++++++++++++++++++++------------------
1 file changed, 81 insertions(+), 60 deletions(-)
--
2.47.1
Powered by blists - more mailing lists