RE: https://mastodon.social/@amutable/115967747219090945

Today, we announce Amutable, our ✨ new ✨ company. We – @blixtra, @brauner, @davidstrauss, @rodrigo_rata, @michaelvogt, @pothos, @zbyszek, @daandemeyer, @cyphar, @jrocha and yours truly – are building the 🚀 next generation of Linux systems, with integrity, determinism, and verification – every step of the way.

https://amutable.com/blog/introducing-amutable

#amutable #linux #systemd #⊼mutable #integrity

@jorge - exactly. Sometimes there are things you know should be done, but you never personally tackle them, because they're too big to take on and/or you just lack the skills.

It takes a team like @amutable to achieve something like this.

@pid_eins @blixtra @brauner @davidstrauss @rodrigo_rata @michaelvogt @pothos @zbyszek @daandemeyer @cyphar @jrocha Sounds interesting. Is the goal based on a threat model? Does "verifiable integrity to Linux systems" mean software and hardware? Or just software?

@tor

The threat model is any exploit (or bug!) that leads to persistent modification of the software stored on disk. The idea is that after a reboot, you _know_ what software was started (or the attestation fails). The hardware is off-the-shelf standard stuff, only needs a TPM. This is about the integrity of the OS and its payload.

@zbyszek Thanks for the explanation. Software integrity is only one side of the coin. The other side is hardware and firmware - see "Bunnie" Huang with his Baochip or UEFI bootkits.