From: Harald Freudenberger <freude@linux.ibm.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Holger Dengler <dengler@linux.ibm.com>,
linux-crypto@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
sparclinux@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH 1/3] crypto: s390 - Remove des and des3_ede code
Date: Thu, 09 Apr 2026 13:02:23 +0200 [thread overview]
Message-ID: <b5ddfc370755c60fbdcfbc954391a088@linux.ibm.com> (raw)
In-Reply-To: <20260327173229.GB3407398@google.com>
On 2026-03-27 18:32, Eric Biggers wrote:
> On Fri, Mar 27, 2026 at 09:52:31AM +0100, Holger Dengler wrote:
>> Hi Eric,
>>
>> On 26/03/2026 21:12, Eric Biggers wrote:
>> > Since DES and Triple DES are obsolete, there is very little point in
>> > maintining architecture-optimized code for them. Remove it.
>> >
>> > Signed-off-by: Eric Biggers <ebiggers@kernel.org>
>>
>> Are there plans to completely remove des/3des in-kernel crypto support
>> from
>> the kernel or is it just the arch-specific code, that is removed?
>
> Just the arch-specific code for now. It will just make these like RC4
> and MD4 which are still implemented for compatibility reasons but only
> with generic C code. Someday (years from now) we should remove all of
> these entirely, but for now the best we can hope for is simplifying the
> implementations to just the generic C code.
>
> - Eric
Reviewed-by: Harald Freudenberger <freude@linux.ibm.com>
next prev parent reply other threads:[~2026-04-09 11:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 20:12 [PATCH 0/3] crypto: Remove arch-optimized des and des3_ede code Eric Biggers
2026-03-26 20:12 ` [PATCH 1/3] crypto: s390 - Remove " Eric Biggers
2026-03-27 8:52 ` Holger Dengler
2026-03-27 17:32 ` Eric Biggers
2026-04-09 11:02 ` Harald Freudenberger [this message]
2026-04-09 7:08 ` Holger Dengler
2026-04-09 7:29 ` John Paul Adrian Glaubitz
2026-04-09 8:22 ` Holger Dengler
2026-04-09 17:48 ` Eric Biggers
2026-03-26 20:12 ` [PATCH 2/3] crypto: sparc " Eric Biggers
2026-03-26 20:12 ` [PATCH 3/3] crypto: x86 " Eric Biggers
2026-03-26 20:20 ` [PATCH 0/3] crypto: Remove arch-optimized " John Paul Adrian Glaubitz
2026-03-26 20:27 ` Eric Biggers
2026-03-26 21:07 ` Eric Biggers
2026-03-27 9:59 ` Simon Richter
2026-03-27 17:24 ` Eric Biggers
2026-04-09 12:46 ` Ard Biesheuvel
2026-04-08 13:35 ` Harald Freudenberger
2026-04-08 13:43 ` John Paul Adrian Glaubitz
2026-04-03 1:07 ` 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=b5ddfc370755c60fbdcfbc954391a088@linux.ibm.com \
--to=freude@linux.ibm.com \
--cc=dengler@linux.ibm.com \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=x86@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