From: Stefan Berger <stefanb@linux.ibm.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: "Coiby Xu" <coxu@redhat.com>,
"Johannes Wiesböck" <johannes.wiesboeck@aisec.fraunhofer.de>,
dhowells@redhat.com, dmitry.kasatkin@gmail.com,
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: Thu, 26 Feb 2026 07:42:00 -0500 [thread overview]
Message-ID: <cba10ac6-3557-4fc1-9b86-55361d14156d@linux.ibm.com> (raw)
In-Reply-To: <20260226001049.GA3135@quark>
On 2/25/26 7:10 PM, Eric Biggers wrote:
> On Wed, Feb 25, 2026 at 09:25:43AM -0500, Stefan Berger wrote:
>> 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...
>
> IMA already had to add its own digest prefixing support, since it was
> needed to disambiguate between full-file digests and fsverity digests.
> See 'struct ima_file_id'. Thus the message signed is at most 66 bytes.
The hash there is still only a hash over a file and that hash is signed,
isn't it?
>
> With that being the case, HashML-DSA isn't necessary. It's not even
> possible to use here, since there are no OIDs assigned for the fsverity
> digests, so it cannot replace the ima_file_id.
For non-fsverify IMA signatures it is 'possible' to use HashML-DSA and
it's 'working' (recycled old patches yesterday):
Linux: https://github.com/stefanberger/linux/commits/dhmlsa%2Bima.202602025/
ima-evm-utils:
https://github.com/linux-integrity/ima-evm-utils/pull/19/commits
>
> I'll also note that HashML-DSA is controversial (e.g. see
> https://keymaterial.net/2024/11/05/hashml-dsa-considered-harmful/),
The problem with this is that NIST would have to react to these
controversies as we race to support PQC. If something is wrong with the
standard then it would be best for NIST to withdraw/modify HashML-DSA
asap. Otherwise it's the best to follow the standard IMO because if you
don't you get criticism otherwise.
> since it was added to the ML-DSA specification at a late stage without
> sufficient review, and what it does can be achieved in better ways.
In case of doubt I would use the standard, though. It's probably not a
good idea for everyone to implement their own (bad) solution.
> Which is exactly what we are seeing here, since again, IMA needs to do
> the digest calculation and prefixing itself anyway.
Use the standard...
Stefan
>
> - Eric
next prev parent reply other threads:[~2026-02-26 12:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 17:43 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 20:31 ` Johannes Wiesböck
2026-02-03 13:32 ` Coiby Xu
2026-02-25 14:25 ` Stefan Berger
2026-02-26 0:10 ` Eric Biggers
2026-02-26 12:42 ` Stefan Berger [this message]
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
2026-01-30 14:10 ` David Howells
2026-02-03 13:43 ` Coiby 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=cba10ac6-3557-4fc1-9b86-55361d14156d@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
all inboxes | Powered by JetHome®