home.social

#verifiedboot — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #verifiedboot, aggregated by home.social.

  1. Information about #SecureBoot and #VerifiedBoot on #Linux systems from the masters of boot, with plenty of diagrams for clarification -->
    blog.3mdeb.com/2025/2025-07-18
    @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

  2. Information about #SecureBoot and #VerifiedBoot on #Linux systems from the masters of boot, with plenty of diagrams for clarification -->
    blog.3mdeb.com/2025/2025-07-18
    @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

  3. Information about #SecureBoot and #VerifiedBoot on #Linux systems from the masters of boot, with plenty of diagrams for clarification.
    blog.3mdeb.com/2025/2025-07-18
    @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.
    That someone could be me with enough time and effort since no one else seems to be doing it. The AOSP (non/semi) closure issue is still 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

  4. Information about #SecureBoot and #VerifiedBoot on #Linux systems from the masters of boot, with plenty of diagrams for clarification -->
    blog.3mdeb.com/2025/2025-07-18
    @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

  5. Information about #SecureBoot and #VerifiedBoot on #Linux systems from the masters of boot, with plenty of diagrams for clarification.
    blog.3mdeb.com/2025/2025-07-18
    @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.
    That someone could be me with enough time and effort since no one else seems to be doing it. The AOSP (non/semi) closure issue is still 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

  6. #VerifiedBoot is a vital security feature that safeguards your device by ensuring the integrity of its system during the boot process.
    By preventing unauthorized changes, it protects against malware, system corruption, and tampering, giving your device an extra layer of #protection. 🔒📱
    With Verified Boot, you're one step ahead in securing your digital world!
    To Get more detail about Verified Boot read our complete #Blog here!👇

    neuronus.net/the-beauty-of-ver

    #MalwareProtection #TamperingPrevention