From: Blaise Boscaccy <bboscaccy@linux.microsoft.com>
To: "Paul Moore" <paul@paul-moore.com>, "Fan Wu" <wufan@kernel.org>,
"Blaise Boscaccy" <bboscaccy@linux.microsoft.com>,
linux-security-module@vger.kernel.org
Subject: [PATCH 3/3] hornet: update signing workflow documentation
Date: Tue, 2 Jun 2026 13:23:22 -0700 [thread overview]
Message-ID: <20260602202336.3579863-4-bboscaccy@linux.microsoft.com> (raw)
In-Reply-To: <20260602202336.3579863-1-bboscaccy@linux.microsoft.com>
After commit cf5d6b993a43 ("hornet: fix TOCTOU in signed program
verification") map indices are no longer passed into gen_sig. Fix the
lingering documentation reference.
Signed-off-by: Blaise Boscaccy <bboscaccy@linux.microsoft.com>
---
Documentation/admin-guide/LSM/Hornet.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/admin-guide/LSM/Hornet.rst b/Documentation/admin-guide/LSM/Hornet.rst
index 13dcf686ead71..6551134d8fd59 100644
--- a/Documentation/admin-guide/LSM/Hornet.rst
+++ b/Documentation/admin-guide/LSM/Hornet.rst
@@ -290,7 +290,7 @@ A typical workflow for building and signing an eBPF light skeleton is:
--key signing_key.pem \
--cert signing_key.x509 \
--data insn.bin \
- --add map.bin:0 \
+ --add map.bin \
--out sig.bin
5. **Embed the signature** back into the header::
--
2.53.0
prev parent reply other threads:[~2026-06-02 20:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 20:23 [PATCH 0/3] hornet: post-TOCTOU-fix cleanup and observability Blaise Boscaccy
2026-06-02 20:23 ` [PATCH 1/3] hornet: log map hash check failures in prog map validation Blaise Boscaccy
2026-06-02 20:23 ` [PATCH 2/3] security, ipe: Remove LSM_INT_VERDICT_UNEXPECTED support Blaise Boscaccy
2026-06-02 20:23 ` Blaise Boscaccy [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=20260602202336.3579863-4-bboscaccy@linux.microsoft.com \
--to=bboscaccy@linux.microsoft.com \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=wufan@kernel.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