From: Stefan Berger <stefanb@linux.ibm.com>
To: "Coiby Xu" <coxu@redhat.com>,
"Johannes Wiesböck" <johannes.wiesboeck@aisec.fraunhofer.de>
Cc: dhowells@redhat.com, dmitry.kasatkin@gmail.com,
ebiggers@kernel.org, eric.snowberg@oracle.com,
keyrings@vger.kernel.org, linux-crypto@vger.kernel.org,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-modules@vger.kernel.org, roberto.sassu@huawei.com,
simo@redhat.com, zohar@linux.ibm.com,
michael.weiss@aisec.fraunhofer.de
Subject: Re: IMA and PQC
Date: Wed, 25 Feb 2026 09:25:43 -0500 [thread overview]
Message-ID: <ee36981d-d658-4296-9acb-874c72606b3e@linux.ibm.com> (raw)
In-Reply-To: <aYHznG6vbptVOjHQ@Rk>
On 2/3/26 8:32 AM, Coiby Xu wrote:
> On Fri, Jan 30, 2026 at 09:31:26PM +0100, Johannes Wiesböck wrote:
>> Hi all,
>
> Hi Johannes,
>
>>
>> we conducted an evaluation regarding PQC use in IMA last year (see [1]
>> for all
>> details) where we also considered the interplay of different PQC
>> signatures and
>> file systems (ext4, btrfs, XFS, f2fs).
>
> Thanks for sharing this comprehensive study! There are many nuances in
> this research paper!
>
>>
>> Coiby Xu <coxu@redhat.com> wrote:
>>
>>> According to my experiments done so far, for verification speed,
>>> ML-DSA-65 is consistently faster than ECDSA P-384 which is used by
>>> current CentOS/RHEL to sign files in a package.
>>
>> Regarding performance, similar to Coiby, we found that all variants of
>> ML-DSA
>> consistently outperformed ECDSA P-256.
>
> Glad to know ML-DSA is also faster than ECDSA P-256!
To avoid duplicate work: Is either one of you planning on writing
patches for IMA to use ML-DSA and convert the current ML-DSA to also
support HashML? I had done the work on this before and could dig out the
patches again...
Stefan
next prev parent reply other threads:[~2026-02-25 14:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 17:43 IMA and PQC David Howells
2026-01-26 21:04 ` Mimi Zohar
2026-01-26 21:36 ` David Howells
2026-01-26 22:54 ` Mimi Zohar
2026-01-30 11:17 ` Coiby Xu
2026-01-30 14:10 ` David Howells
2026-02-03 13:43 ` Coiby Xu
2026-01-30 20:31 ` Johannes Wiesböck
2026-02-03 13:32 ` Coiby Xu
2026-02-25 14:25 ` Stefan Berger [this message]
2026-02-26 0:10 ` Eric Biggers
2026-02-26 12:42 ` Stefan Berger
2026-02-26 14:16 ` Stefan Berger
2026-02-26 15:27 ` Simo Sorce
2026-02-26 16:58 ` Eric Biggers
2026-02-26 17:22 ` Stefan Berger
2026-02-26 18:32 ` Eric Biggers
2026-02-26 19:21 ` Stefan Berger
2026-02-26 19:44 ` Eric Biggers
2026-02-26 21:05 ` Stefan Berger
2026-02-26 18:42 ` Simo Sorce
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=ee36981d-d658-4296-9acb-874c72606b3e@linux.ibm.com \
--to=stefanb@linux.ibm.com \
--cc=coxu@redhat.com \
--cc=dhowells@redhat.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=ebiggers@kernel.org \
--cc=eric.snowberg@oracle.com \
--cc=johannes.wiesboeck@aisec.fraunhofer.de \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=michael.weiss@aisec.fraunhofer.de \
--cc=roberto.sassu@huawei.com \
--cc=simo@redhat.com \
--cc=zohar@linux.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox