From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
bpf@vger.kernel.org, linux-crypto@vger.kernel.org
Cc: "Jason A. Donenfeld" <Jason@zx2c4.com>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Andy Lutomirski <luto@amacapital.net>,
Ard Biesheuvel <ardb@kernel.org>, Erik Kline <ek@google.com>,
Fernando Gont <fgont@si6networks.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Hannes Frederic Sowa <hannes@stressinduktion.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
Jean-Philippe Aumasson <jeanphilippe.aumasson@gmail.com>,
Lorenzo Colitti <lorenzo@google.com>
Subject: [PATCH RFC v2 0/3] remove remaining users of SHA-1
Date: Fri, 14 Jan 2022 15:20:12 +0100 [thread overview]
Message-ID: <20220114142015.87974-1-Jason@zx2c4.com> (raw)
Hi,
There are currently two remaining users of SHA-1 left in the kernel: bpf
tag generation, and ipv6 address calculation. In an effort to reduce
code size and rid ourselves of insecure primitives, this RFC patchset
moves to using the more secure BLAKE2s function. I wanted to get your
feedback on how feasible this patchset is, and if there is some
remaining attachment to SHA-1, why exactly, and what could be done to
mitigate it. Rather than sending a mailing list post just asking, "what
do you think?" I figured it'd be easier to send this as an RFC patchset,
so you see specifically what I mean.
Version 2 makes the ipv6 handling a bit cleaner and fixes a build
warning from the last commit. Since this is just an RFC-for-discussion,
there's not technically a need to be sending this, but from the looks of
it, a real solution here might involve a bit more heavy lifting, so I
wanted to at least get my latest on the list in case others want to play
around with solutions in this space too. Also, the original recipient
list was too narrow, so this v2 expands that a bit.
Thoughts? Comments?
Thanks,
Jason
Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Andy Lutomirski <luto@amacapital.net>
Cc: Ard Biesheuvel <ardb@kernel.org>
Cc: Erik Kline <ek@google.com>
Cc: Fernando Gont <fgont@si6networks.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Hannes Frederic Sowa <hannes@stressinduktion.org>
Cc: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Jean-Philippe Aumasson <jeanphilippe.aumasson@gmail.com>
Cc: Lorenzo Colitti <lorenzo@google.com>
Jason A. Donenfeld (3):
bpf: move from sha1 to blake2s in tag calculation
ipv6: move from sha1 to blake2s in address calculation
crypto: sha1_generic - import lib/sha1.c locally
crypto/sha1_generic.c | 182 +++++++++++++++++++++++++++++++++++++
include/crypto/sha1.h | 10 ---
kernel/bpf/core.c | 39 +-------
lib/Makefile | 2 +-
lib/sha1.c | 204 ------------------------------------------
net/ipv6/addrconf.c | 56 +++---------
6 files changed, 201 insertions(+), 292 deletions(-)
delete mode 100644 lib/sha1.c
--
2.34.1
next reply other threads:[~2022-01-14 14:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 14:20 Jason A. Donenfeld [this message]
2022-01-14 14:20 ` [PATCH RFC v2 1/3] bpf: move from sha1 to blake2s in tag calculation Jason A. Donenfeld
2022-01-14 16:20 ` Alexei Starovoitov
2022-01-14 16:33 ` Jason A. Donenfeld
2022-01-14 14:20 ` [PATCH RFC v2 2/3] ipv6: move from sha1 to blake2s in address calculation Jason A. Donenfeld
2022-01-14 14:20 ` [PATCH RFC v2 3/3] crypto: sha1_generic - import lib/sha1.c locally Jason A. Donenfeld
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220114142015.87974-1-Jason@zx2c4.com \
--to=jason@zx2c4.com \
--cc=alexei.starovoitov@gmail.com \
--cc=ardb@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=ek@google.com \
--cc=fgont@si6networks.com \
--cc=geert@linux-m68k.org \
--cc=hannes@stressinduktion.org \
--cc=herbert@gondor.apana.org.au \
--cc=jeanphilippe.aumasson@gmail.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo@google.com \
--cc=luto@amacapital.net \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome