Information about #SecureBoot and #VerifiedBoot on #Linux systems from the masters of boot, with plenty of diagrams for clarification -->
https://blog.3mdeb.com/2025/2025-07-18-securing-embedded-linux/
@3mdeb
Mobile FOSS-friendly developers could be very helpful by creating a similar explanation about what is "open" and what is "closed," who gets what permissions where, what is proprietary, what is manufacturer controlled and what is owner controlled, etc, and compare #GrapheneOS to #PostMarketOS, #UbuntuTouch, iPhone, and Mobian. @debian
That someone could be me with enough time and effort since no one else seems to be doing it. But it would be quite the study and a comprehensive explanation would require extensive research. The AOSP (non/semi) closure issue remains unclear to many people.
Why can't people just have a good Linux phone with full read write permissions and control their own crypto keys as it the case for workstations?
@postmarketOS