From: Harald Freudenberger <freude@linux.ibm.com>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Eric Biggers <ebiggers@kernel.org>,
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,
Holger Dengler <dengler@linux.ibm.com>
Subject: Re: [PATCH 0/3] crypto: Remove arch-optimized des and des3_ede code
Date: Wed, 08 Apr 2026 15:35:13 +0200 [thread overview]
Message-ID: <ccb1363db0aa040838396090155b3e66@linux.ibm.com> (raw)
In-Reply-To: <0982d4341f58e2f1181bc472dc9c9d8542148e3c.camel@physik.fu-berlin.de>
On 2026-03-26 21:20, John Paul Adrian Glaubitz wrote:
> On Thu, 2026-03-26 at 13:12 -0700, Eric Biggers wrote:
>> DES and 3DES are cryptographically obsolete and insecure by modern
>> standards. Continuing to maintain highly specific, complex assembly
>> and
>> glue code for them, especially when the code isn't testable in QEMU
>> (s390 and sparc), is unnecessary and risky.
>
> We're working on getting crypto instructions added to QEMU though.
>
> Adrian
Hi Adrian
I am about to implement some of the cpacf instructions for qemu.
Eric and others complained about being unable to test the s390 in-kernel
crypto
implementations and thus I am about to improve this. As soon as my patch
series
is in a good shape I'll forward it to you. As of now my main focus is on
AES (ECB,
CTR, CBC, XTS) with and without protected key support.
Please let us not do this work twice - so get in contact with me and
Holger
about possible s390 specific crypto implementations for qemu.
Harald Freudenberger
next prev parent reply other threads:[~2026-04-08 13:35 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
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 [this message]
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=ccb1363db0aa040838396090155b3e66@linux.ibm.com \
--to=freude@linux.ibm.com \
--cc=dengler@linux.ibm.com \
--cc=ebiggers@kernel.org \
--cc=glaubitz@physik.fu-berlin.de \
--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