From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: "Ard Biesheuvel" <ardb@kernel.org>,
"Toke Høiland-Jørgensen" <toke@redhat.com>,
"Network Development" <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"Jean-Philippe Aumasson" <jeanphilippe.aumasson@gmail.com>,
"Linux Crypto Mailing List" <linux-crypto@vger.kernel.org>,
bpf <bpf@vger.kernel.org>
Subject: Re: [PATCH RFC v1 1/3] bpf: move from sha1 to blake2s in tag calculation
Date: Fri, 14 Jan 2022 17:34:44 +0100 [thread overview]
Message-ID: <CAHmME9pHhy7sXfkF7LWPDik3obkgwYZd1BRSVMYx5=uFAuQtOQ@mail.gmail.com> (raw)
In-Reply-To: <CAADnVQKCSJi=U4gNv48vsS8Guu7_JP946yMuNqVAJ-D=rAme7w@mail.gmail.com>
On Fri, Jan 14, 2022 at 5:19 PM Alexei Starovoitov
<alexei.starovoitov@gmail.com> wrote:
>
> On Fri, Jan 14, 2022 at 7:08 AM Ard Biesheuvel <ardb@kernel.org> wrote:
> >
> > Yeah, so the issue is that, at *some* point, SHA-1 is going to have to
> > go.
>
> sha1 cannot be removed from the kernel.
> See AF_ALG and iproute2 source for reference.
It can be removed from vmlinux, and be folded into the crypto API's
generic implementation where it belongs, which then can be built as a
module or not built at all, depending on configuration. Please see the
3/3 patch in this series to see what that looks like:
https://lore.kernel.org/lkml/20220114142015.87974-4-Jason@zx2c4.com/
Meanwhile, you have not replied to any of the substantive issues I
brought up. I'd appreciate you doing so.
Thank you,
Jason
next prev parent reply other threads:[~2022-01-14 16:35 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 13:12 [PATCH RFC v1 0/3] remove remaining users of SHA-1 Jason A. Donenfeld
2022-01-12 13:12 ` [PATCH RFC v1 1/3] bpf: move from sha1 to blake2s in tag calculation Jason A. Donenfeld
2022-01-12 22:56 ` Toke Høiland-Jørgensen
2022-01-13 1:33 ` Alexei Starovoitov
2022-01-13 12:27 ` Jason A. Donenfeld
2022-01-13 22:45 ` Alexei Starovoitov
2022-01-14 8:33 ` Geert Uytterhoeven
2022-01-14 14:12 ` Jason A. Donenfeld
2022-01-14 15:08 ` Ard Biesheuvel
2022-01-14 15:20 ` Jason A. Donenfeld
2022-01-14 15:36 ` Geert Uytterhoeven
2022-01-14 15:59 ` David Laight
2022-01-14 16:19 ` Alexei Starovoitov
2022-01-14 16:34 ` Jason A. Donenfeld [this message]
2022-01-14 23:04 ` Jeffrey Walton
2022-01-12 13:12 ` [PATCH RFC v1 2/3] ipv6: move from sha1 to blake2s in address calculation Jason A. Donenfeld
2022-01-12 15:49 ` Jason A. Donenfeld
2022-01-12 23:05 ` Toke Høiland-Jørgensen
2022-01-12 23:31 ` Jason A. Donenfeld
2022-01-13 11:15 ` Hannes Frederic Sowa
2022-01-13 12:06 ` Ard Biesheuvel
2022-01-13 12:22 ` Jason A. Donenfeld
2022-01-13 12:29 ` Ard Biesheuvel
2022-01-13 13:30 ` Toke Høiland-Jørgensen
2022-01-13 13:40 ` Ard Biesheuvel
2022-01-13 13:45 ` Jason A. Donenfeld
2022-01-13 13:50 ` Ard Biesheuvel
2022-01-13 13:54 ` Jason A. Donenfeld
2022-01-13 16:18 ` Toke Høiland-Jørgensen
2022-01-14 16:07 ` Jason A. Donenfeld
2022-01-14 16:57 ` Toke Høiland-Jørgensen
2022-01-14 17:41 ` Hannes Frederic Sowa
2022-01-14 17:58 ` Jason A. Donenfeld
2022-01-12 13:12 ` [PATCH RFC v1 3/3] crypto: sha1_generic - import lib/sha1.c locally Jason A. Donenfeld
2022-01-12 18:50 ` [PATCH RFC v1 0/3] remove remaining users of SHA-1 David Sterba
2022-01-12 18:57 ` Jason A. Donenfeld
2022-01-13 3:24 ` Sandy Harris
2022-01-13 8:08 ` Ard Biesheuvel
2022-01-13 17:28 ` Theodore Ts'o
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='CAHmME9pHhy7sXfkF7LWPDik3obkgwYZd1BRSVMYx5=uFAuQtOQ@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=alexei.starovoitov@gmail.com \
--cc=ardb@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=geert@linux-m68k.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=netdev@vger.kernel.org \
--cc=toke@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.