From: Maxime MERE <maxime.mere@foss.st.com>
To: Eric Biggers <ebiggers@kernel.org>, <linux-fscrypt@vger.kernel.org>
Cc: <linux-crypto@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-mtd@lists.infradead.org>, <linux-ext4@vger.kernel.org>,
<linux-f2fs-devel@lists.sourceforge.net>,
<ceph-devel@vger.kernel.org>
Subject: Re: [PATCH] fscrypt: don't use hardware offload Crypto API drivers
Date: Fri, 13 Jun 2025 11:01:03 +0200 [thread overview]
Message-ID: <8f4c2f36-71af-4c84-bcee-2554cea991d0@foss.st.com> (raw)
In-Reply-To: <20250611205859.80819-1-ebiggers@kernel.org>
Hello,
On 6/11/25 22:58, Eric Biggers wrote:
> To protect users from these buggy and seemingly unhelpful drivers that I
> have no way of testing, let's make fscrypt not use them. Unfortunately
> there is no direct support for doing so in the Crypto API, but we can
> achieve something very close to it by disallowing algorithms that have
> ASYNC, ALLOCATES_MEMORY, or KERN_DRIVER_ONLY set.
I agree that software drivers are more efficient and less prone to bugs
than hardware drivers. However, I would like to highlight the fact that
certain ST products (the STM32MP2x series) have features that allow the
loading of a secret key via an internal bus from a Secure OS to the CRYP
peripheral (usable by the kernel). This enables cryptographic operations
to be delegated to the non-secure side (the kernel) without exposing the
key.
If fscrypt no longer supports hardware drivers, then this type of
functionality could not be used, which I find unfortunate because it is
something that might interest users.
cheers,
Maxime
next prev parent reply other threads:[~2025-06-13 9:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 20:58 Eric Biggers
2025-06-12 0:21 ` Simon Richter
2025-06-12 0:59 ` Eric Biggers
2025-06-12 6:25 ` Eric Biggers
2025-06-12 8:50 ` Giovanni Cabiddu
2025-06-12 15:57 ` Eric Biggers
2025-06-13 1:23 ` Eric Biggers
2025-06-13 11:10 ` Giovanni Cabiddu
2025-06-25 6:32 ` Eric Biggers
2025-06-25 12:44 ` Theodore Ts'o
2025-06-25 18:38 ` Eric Biggers
2025-06-25 16:29 ` Maxime MERE
2025-06-25 19:17 ` Eric Biggers
2025-06-13 9:01 ` Maxime MERE [this message]
2025-06-13 14:42 ` Eric Biggers
2025-06-25 16:29 ` Maxime MERE
2025-06-25 18:57 ` Eric Biggers
2025-06-26 2:36 ` Eric Biggers
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=8f4c2f36-71af-4c84-bcee-2554cea991d0@foss.st.com \
--to=maxime.mere@foss.st.com \
--cc=ceph-devel@vger.kernel.org \
--cc=ebiggers@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fscrypt@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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
all inboxes | Powered by JetHome®