Having worked on the kernel for decades, and imposing a lot of the same code/git hygiene for liburing, there can be a disconnect for contributors on what is expected of a commit and commit message, and what series of commits should look like. I attempted to provide a basic guideline here:
https://github.com/axboe/liburing/blob/master/CONTRIBUTING.md
and would appreciate feedback from folks on what I missed, what isn't clear, etc.
Gonna be giving a talk "SLUB Internals for Exploit Developers" at @LinuxSecSummit next week.
Plan to cover the basics one needs to know before writing exploits for slab bugs; slides coming along 😁
Also gonna stay around for @linuxplumbersconf.
@josh after 15 years of TPMs and they becoming quite ubiquitious, I am still not seeing how they ever have been misused like this outside of theories and labs.
To me this appears to be mostly FUD from FSF/GNU.
I think if Linux OSes would actually start using TPMs properly, the net outcome for everyone would be *good*, and not bad. It would be much harder to gain persistence for an attacker, for example. And that's a massive benefit, for everyone.
the debugging manifesto poster I've been talking about is finally available for sale! You can get it here for $20 US + shipping: https://store.wizardzines.com/products/poster-debugging-manifesto
it was redesigned and riso printed by Inner Loop Press and I'm SO delighted with how it turned out (https://www.innerloop.press/)
Just published the #ASG2024 schedule! Lots of good stuff, and at least one terrible talk that nobody should attend.
Early bird tickets are also still available - but not for long - go grab them while they last!
It's been a while since the last one, but here is the fourth #Landlock newsletter: https://lore.kernel.org/landlock/20240716.yui4Iezai8ae@digikod.net/
Moar sandboxing! 🥳
Another relatively small update, but here are the LSM, SELinux, and audit* highlights from the Linux v6.11 merge window.
https://paul-moore.com/blog/d/2024/07/linux_v611_merge_window.html
There are three hard things in computer science: cache invalidation, naming things, and getting your video game character onto a ladder.