From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: ast@kernel.org, kpsingh@kernel.org,
James.Bottomley@hansenpartnership.com, paul@paul-moore.com,
bboscaccy@linux.microsoft.com, memxor@gmail.com,
torvalds@linux-foundation.org, a.s.protopopov@gmail.com,
bpf@vger.kernel.org, linux-security-module@vger.kernel.org
Subject: Re: [PATCH bpf-next v6 0/8] Verify BPF signed loader at load time
Date: Wed, 08 Jul 2026 18:30:16 +0000 [thread overview]
Message-ID: <178353541664.3057345.9896047455904217211.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260708075343.358712-1-daniel@iogearbox.net>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:
On Wed, 8 Jul 2026 09:53:35 +0200 you wrote:
> The BPF signing scheme signs a light skeleton's loader program and lets
> the loader vouch for everything else: bpftool bakes the SHA256 of the
> metadata map into the loader's instructions, signs the instructions, and
> the loader compares the (frozen, exclusive) map against that hash from
> within BPF once it runs. The construction is sound as a trusted hash
> chain, but the kernel itself never attests the metadata, and that split
> has been the recurring objection from the LSM / integrity side since the
> scheme was proposed.
>
> [...]
Here is the summary with links:
- [bpf-next,v6,1/8] bpf: Resolve and cache fd_array objects at load time
https://git.kernel.org/bpf/bpf-next/c/d5a85392392c
- [bpf-next,v6,2/8] bpf: Verify signed loader metadata at load time
https://git.kernel.org/bpf/bpf-next/c/b707068e0ed9
- [bpf-next,v6,3/8] libbpf: Drop in-loader metadata check for load-time verification
https://git.kernel.org/bpf/bpf-next/c/a2d784869a0f
- [bpf-next,v6,4/8] bpftool: Check EVP_Digest when computing excl_prog_hash
https://git.kernel.org/bpf/bpf-next/c/576bcaa1f5c2
- [bpf-next,v6,5/8] bpftool: Cover loader metadata with the program signature
https://git.kernel.org/bpf/bpf-next/c/92c7717981bb
- [bpf-next,v6,6/8] selftests/bpf: Adjust bpf_map layout in verifier_map_ptr
https://git.kernel.org/bpf/bpf-next/c/77e5f3c91453
- [bpf-next,v6,7/8] selftests/bpf: Verify load-time signed loader metadata
https://git.kernel.org/bpf/bpf-next/c/99b321dde704
- [bpf-next,v6,8/8] Documentation/bpf: Add BPF signing and enforcement doc
https://git.kernel.org/bpf/bpf-next/c/84c42f515f18
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-07-08 18:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 7:53 [PATCH bpf-next v6 0/8] Verify BPF signed loader at load time Daniel Borkmann
2026-07-08 7:53 ` [PATCH bpf-next v6 1/8] bpf: Resolve and cache fd_array objects " Daniel Borkmann
2026-07-08 7:53 ` [PATCH bpf-next v6 2/8] bpf: Verify signed loader metadata " Daniel Borkmann
2026-07-08 7:53 ` [PATCH bpf-next v6 3/8] libbpf: Drop in-loader metadata check for load-time verification Daniel Borkmann
2026-07-08 8:15 ` sashiko-bot
2026-07-08 8:20 ` Daniel Borkmann
2026-07-08 7:53 ` [PATCH bpf-next v6 4/8] bpftool: Check EVP_Digest when computing excl_prog_hash Daniel Borkmann
2026-07-08 8:55 ` Quentin Monnet
2026-07-08 7:53 ` [PATCH bpf-next v6 5/8] bpftool: Cover loader metadata with the program signature Daniel Borkmann
2026-07-08 8:55 ` Quentin Monnet
2026-07-08 7:53 ` [PATCH bpf-next v6 6/8] selftests/bpf: Adjust bpf_map layout in verifier_map_ptr Daniel Borkmann
2026-07-08 8:14 ` sashiko-bot
2026-07-08 8:16 ` Daniel Borkmann
2026-07-08 7:53 ` [PATCH bpf-next v6 7/8] selftests/bpf: Verify load-time signed loader metadata Daniel Borkmann
2026-07-08 8:07 ` sashiko-bot
2026-07-08 8:26 ` Daniel Borkmann
2026-07-08 7:53 ` [PATCH bpf-next v6 8/8] Documentation/bpf: Add BPF signing and enforcement doc Daniel Borkmann
2026-07-08 18:30 ` patchwork-bot+netdevbpf [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=178353541664.3057345.9896047455904217211.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=James.Bottomley@hansenpartnership.com \
--cc=a.s.protopopov@gmail.com \
--cc=ast@kernel.org \
--cc=bboscaccy@linux.microsoft.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kpsingh@kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=memxor@gmail.com \
--cc=paul@paul-moore.com \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.