ity [unit X-69] - VIOLENT FUCK on Nostr: I need to look into details about measured boot impl within Android (also note my ...

I need to look into details about measured boot impl within Android (also note my comment about measured boot != secure boot; secure boot doesn't work on most consumer ARM devices, aka cannot "relock" (unless it's a Pixel, afaik)

For context, I work on measured boot for Linux, both x86 and ARM, the main issue is that while we can get that working on pmOS, what we can't get working is the large ecosystem of apps that are explicitly written against an API that is security-first, unlike Linux apps that are written assuming full access and shit the bed otherwise, requiring all kinds of workarounds. Portals are reinventing (badly) what Android was doing back with eg. SAF, and they aren't nearly restrictive enough.

If you wanted FD.O phones to be as secure, you'd need to get an ecosystem of apps written by devs that accept using a security-first API, and a competent team to design and impl the API, then reimplement a secure framework below it, package it all so that it integrates with the OTA model and integrity/verity, implement proper app signatures and a system for app distribution, get it all working with SELinux and UIDs and everything else...

And by then you have basically reinvented Android, except probably forgot about 10 different things that Android already solved cuz it has been on this since 2008

I'm not saying give up; I'm saying use Android as the base and fix the Google fuckups, or properly understand how and why Android does the ways it does security things (99% of the time, Android itself has actual reasons for basically everything; Google limits its malware shit to Play Services and keeps Android basically pure engineering work, no management making it broken. Meaning the main fuckups are bad performance optimizations, horrible UX... They don't really have a big competent UX team). Even the silly Google developer certificate system has a use (for example, could use it with a distributed signing system, and allow things like, signing apps with ACME; so you could eg. verify that a given apk with the package name com.example.cuteandfunnyapp is verified by whoever controls example.com, amongst other things. Once again, it's Android making a good thing, Google's Play Services using it for something stupid to make it the most useless possible, and then techbros blaming Android for it, despite as said above, it's actually a really good, albeit overengineered system. Google then picks the most clueless PR person to speak to the techbros and that's how you get the shitstorms.)