Comment on Android 14 blocks all modification of system certificates, even as root

Semi-Hemi-Demigod@kbin.social ⁨1⁩ ⁨year⁩ ago

• Kyrgizion@lemmy.world ⁨1⁩ ⁨year⁩ ago

  Pseudo-Sudo

  source

  • Sibbo@sopuli.xyz ⁨1⁩ ⁨year⁩ ago

    psudo

    source
  • BruceWang@lemmy.world ⁨1⁩ ⁨year⁩ ago

    Sudowoodo

    source
  • Ertebolle@kbin.social ⁨1⁩ ⁨year⁩ ago

    Psu Psu Psudsudo

    source

    • lingh0e@lemmy.film ⁨1⁩ ⁨year⁩ ago

      Woh-oh-ohoh!

      source
• MyFairJulia@lemmy.world ⁨1⁩ ⁨year⁩ ago

  Perhaps LineageOS could help. Or GrapheneOS.

  source

  • Melpomene@kbin.social ⁨1⁩ ⁨year⁩ ago

    I'll be watching to see how Graphene handles this, as Graphene is currently my daily driver.

    source

    • vcmj@programming.dev ⁨1⁩ ⁨year⁩ ago

      They previously did not use APEX but that seems to have changed recently: https://github.com/GrapheneOS/grapheneos.org/commit/7bf9b2671667828d1553c92bf4f64cc749b74d0b Regardless it will need the verified boot keys it seems so Google can’t update them, likely the devs will take responsibility to update the CAs. No idea if they will restore the user control though.

      source
• Ertebolle@kbin.social ⁨1⁩ ⁨year⁩ ago

  What is root if not supervisor persevering?

  source

  • muse@kbin.social ⁨1⁩ ⁨year⁩ ago

    I understood that reference

    source