Taming the BPF Superpowers
lwn.net
lwn.net
Slides: https://linuxplumbersconf.org/event/11/contributions/947/att...
I always found it a bit odd that Linux doesn't have a standard binary signing mechanism, like Windows does through Authenticode (well, and Catalog signatures, and now a different scheme for UWL apps too).
I guess it's not quite as necessary, since on Linux you typically get apps from trusted package repositories, but personally it's still something I'd like to see, so file integrity could be verified later (even offline if wanted).
I'm not entirely sure if techniques such as ASLR are fool-proof enough to prevent changes to binaries in memory - I haven't studied enough about ASLR yet.
PGP is typically used to sign a collection of hashes (and other metadata). PGP is generally only used at package install/build time, and the subsequently installed/generated manifest is used when you ask the package manager to verify the package.
That said, rpm supports package signing, so that it can catch a package which was tampered with and prevent it's installation.
eBPF is great for tracing but there's only so much you can do without really injecting yourself into the target binary.
All good so far, but the moment I wanted to do a little bit of non-trivial work (collect some metadata which is not a memory access away) I would've had to switch to some other much more complicated system. I don't think Pin is that complicated but it's not really intended for "infra" programming like eBPF.
Kids, always define all acronyms when first using them in technical writing, as in: Work toward the signing of Big Pill Foundation (BPF) programs has been finding its way into recent mainline kernel releases...
In theory, the kernel people could come up with a new acronym (something like Kernel Bytecode Language might be appropriate), but at this point it's probably too late.
Also, it’s safe to assume that regular readers of LWN will know a little about BPF. Though obviously in this case it rose to the top of HN where it’s likely to be seen by a wider audience.
It's was originally eBPF and that doesnt really tell you any more. Now we've dropped the 'e' and its turned in to an initialism unrelated to the original network related only functionality as others have said.
Im curious what others would call these if they could rename them...
Kernel Plugins?
Kernel Spies?
Advanced observability operators?