From: Mike Snitzer <snitzer@redhat.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Eric Biggers <ebiggers@kernel.org>,
agk@redhat.com, dm-devel@redhat.com,
Milan Broz <gmazyland@gmail.com>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: [PATCH 5/5] crypto: remove Salsa20 stream cipher algorithm
Date: Thu, 21 Jan 2021 13:20:35 -0500 [thread overview]
Message-ID: <20210121182035.GB4662@redhat.com> (raw)
In-Reply-To: <CAMj1kXEycOHSMQu2T1tdQrmapk+g0oQFDiWXDo0J0BKg4QgEuQ@mail.gmail.com>
On Thu, Jan 21 2021 at 1:09pm -0500,
Ard Biesheuvel <ardb@kernel.org> wrote:
> On Thu, 21 Jan 2021 at 19:05, Eric Biggers <ebiggers@kernel.org> wrote:
> >
> > On Thu, Jan 21, 2021 at 02:07:33PM +0100, Ard Biesheuvel wrote:
> > > Salsa20 is not used anywhere in the kernel, is not suitable for disk
> > > encryption, and widely considered to have been superseded by ChaCha20.
> > > So let's remove it.
> > >
> > > Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
> > > ---
> > > Documentation/admin-guide/device-mapper/dm-integrity.rst | 4 +-
> > > crypto/Kconfig | 12 -
> > > crypto/Makefile | 1 -
> > > crypto/salsa20_generic.c | 212 ----
> > > crypto/tcrypt.c | 11 +-
> > > crypto/testmgr.c | 6 -
> > > crypto/testmgr.h | 1162 --------------------
> > > 7 files changed, 3 insertions(+), 1405 deletions(-)
> > >
> > > diff --git a/Documentation/admin-guide/device-mapper/dm-integrity.rst b/Documentation/admin-guide/device-mapper/dm-integrity.rst
> > > index 4e6f504474ac..d56112e2e354 100644
> > > --- a/Documentation/admin-guide/device-mapper/dm-integrity.rst
> > > +++ b/Documentation/admin-guide/device-mapper/dm-integrity.rst
> > > @@ -143,8 +143,8 @@ recalculate
> > > journal_crypt:algorithm(:key) (the key is optional)
> > > Encrypt the journal using given algorithm to make sure that the
> > > attacker can't read the journal. You can use a block cipher here
> > > - (such as "cbc(aes)") or a stream cipher (for example "chacha20",
> > > - "salsa20" or "ctr(aes)").
> > > + (such as "cbc(aes)") or a stream cipher (for example "chacha20"
> > > + or "ctr(aes)").
> >
> > You should check with the dm-integrity maintainers how likely it is that people
> > are using salsa20 with dm-integrity. It's possible that people are using it,
> > especially since the documentation says that dm-integrity can use a stream
> > cipher and specifically gives salsa20 as an example.
> >
>
> Good point - cc'ed them now.
>
No problem here, if others don't find utility in salsa20 then
dm-integrity certainly isn't the hold-out.
Acked-by: Mike Snitzer <snitzer@redhat.com>
Mike
next prev parent reply other threads:[~2021-01-21 18:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 13:07 [PATCH 0/5] crypto: remove some obsolete algorithms Ard Biesheuvel
2021-01-21 13:07 ` [PATCH 1/5] crypto: remove RIPE-MD 128 hash algorithm Ard Biesheuvel
2021-01-21 13:07 ` [PATCH 2/5] crypto: remove RIPE-MD 256 " Ard Biesheuvel
2021-01-21 13:07 ` [PATCH 3/5] crypto: remove RIPE-MD 320 " Ard Biesheuvel
2021-01-21 13:07 ` [PATCH 4/5] crypto: remove Tiger 128/160/192 hash algorithms Ard Biesheuvel
2021-01-21 13:07 ` [PATCH 5/5] crypto: remove Salsa20 stream cipher algorithm Ard Biesheuvel
2021-01-21 18:05 ` Eric Biggers
2021-01-21 18:09 ` Ard Biesheuvel
2021-01-21 18:20 ` Mike Snitzer [this message]
2021-01-21 18:23 ` Milan Broz
2021-01-29 5:10 ` [PATCH 0/5] crypto: remove some obsolete algorithms Herbert Xu
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=20210121182035.GB4662@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=ardb@kernel.org \
--cc=dm-devel@redhat.com \
--cc=ebiggers@kernel.org \
--cc=gmazyland@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@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;
as well as URLs for NNTP newsgroup(s).