From: Milan Broz <gmazyland@gmail.com>
To: "Mike Luken (mluken)" <mluken@cisco.com>,
"cryptsetup@lists.linux.dev" <cryptsetup@lists.linux.dev>
Subject: Re: LMS verification support
Date: Mon, 12 Dec 2022 09:10:31 +0100 [thread overview]
Message-ID: <70676296-dc41-b8f5-cb4d-6b7657e8a806@gmail.com> (raw)
In-Reply-To: <95080015-BD73-49C4-88D0-23502B75A532@cisco.com>
On 12/2/22 16:06, Mike Luken (mluken) wrote:
> NIST and NSA have both recommended the use of the LMS algorithm for
> firmware and software signatures and verification. NSA stated
> vendors should have this supported in products in 2025. What are the
> plans to add LMS support into the kernel for things like secure boot
> (I guess this is done via the SHIM which I don’t know if this is
> covered by kernel.org or not) , signed kernel modules and IMA?
This is really not a question for this list, I guess you should write
to some kernel list (I guess kernel-integrity, archive here
https://lore.kernel.org/linux-integrity/ )
Milan
prev parent reply other threads:[~2022-12-12 8:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 15:06 LMS verification support Mike Luken (mluken)
2022-12-12 8:10 ` Milan Broz [this message]
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=70676296-dc41-b8f5-cb4d-6b7657e8a806@gmail.com \
--to=gmazyland@gmail.com \
--cc=cryptsetup@lists.linux.dev \
--cc=mluken@cisco.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;
as well as URLs for NNTP newsgroup(s).