#Linux kernel maintainers propose a less painful process for identifying developers and their code, making it safer than ever.
@sjvn @ZDNet A few observations:
* security technologies don't age well: at our original 2011 keysigning, sha1 was the usual signature hash, so that's the hash we use for most of the kernel web of trust.
* Introducing a new mechanism for kernel developers at a conference none of them go to isn't guaranteed to be influential
* short expiration isn't that popular and it often doesn't interact well with required historical use: https://lore.kernel.org/ksummit/CAHk-=[email protected]/
@sjvn It's somewhat like @linuxplumbersconf technically a LF event but tightly controlled by its planning committee. The LSF/MM committee were in the CFP
https://lore.kernel.org/all/20260110-lsfmm-2026-cfp-ae970765d60e@brauner/
You can use the PC email they advertise to contact them