From: Paul Moore <paul@paul-moore.com>
To: ryan foster <foster.ryan.r@gmail.com>
Cc: bboscaccy@linux.microsoft.com,
James.Bottomley@hansenpartnership.com,
akpm@linux-foundation.org, bpf@vger.kernel.org, corbet@lwn.net,
dhowells@redhat.com, gnoack@google.com, jmorris@namei.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, linux@treblig.org,
mic@digikod.net, serge@hallyn.com
Subject: Re: [RFC 00/11] Reintroduce Hornet LSM
Date: Tue, 16 Dec 2025 21:27:39 -0500 [thread overview]
Message-ID: <CAHC9VhQ4=ALurNy_nBdqmdQ1dguupPnJ6KYAnU7B2UWhp9ydbA@mail.gmail.com> (raw)
In-Reply-To: <CAHtS32-Zh3knxSdR=DUqQH4rX4QU8ewgu+KHGq6Af3qs9S0FAg@mail.gmail.com>
On Mon, Dec 15, 2025 at 12:26 PM ryan foster <foster.ryan.r@gmail.com> wrote:
>
> Hi all,
>
> I want to confirm I understand the current semantics, and specific issues this series is addressing.
I don't want to speak for Blaise (or James for that matter), but my
understanding is that Hornet is focused on ensuring BPF program
integrity at load time; similar to KP's signature scheme which has
recently found its way into Linus tree. Where KP's and Blaise's
scheme differ is in how they perform the integrity checks.
--
paul-moore.com
next parent reply other threads:[~2025-12-17 2:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHtS32-Zh3knxSdR=DUqQH4rX4QU8ewgu+KHGq6Af3qs9S0FAg@mail.gmail.com>
2025-12-17 2:27 ` Paul Moore [this message]
2025-12-17 19:33 ` [RFC 00/11] Reintroduce Hornet LSM Blaise Boscaccy
2025-12-11 2:11 Blaise Boscaccy
2025-12-15 17:45 ` Ryan Foster
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='CAHC9VhQ4=ALurNy_nBdqmdQ1dguupPnJ6KYAnU7B2UWhp9ydbA@mail.gmail.com' \
--to=paul@paul-moore.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=bboscaccy@linux.microsoft.com \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=dhowells@redhat.com \
--cc=foster.ryan.r@gmail.com \
--cc=gnoack@google.com \
--cc=jmorris@namei.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux@treblig.org \
--cc=mic@digikod.net \
--cc=serge@hallyn.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).