@[email protected] to [email protected] • 2 years agoAndroid 14 blocks all modification of system certificates, even as roothttptoolkit.comexternal-linkmessage-square59fedilinkarrow-up1266cross-posted to: [email protected][email protected][email protected][email protected]
arrow-up1266external-linkAndroid 14 blocks all modification of system certificates, even as roothttptoolkit.com@[email protected] to [email protected] • 2 years agomessage-square59fedilinkcross-posted to: [email protected][email protected][email protected][email protected]
minus-squareMelpomenelinkfedilink22•2 years agoI’ll be watching to see how Graphene handles this, as Graphene is currently my daily driver.
minus-square@[email protected]linkfedilink7•2 years agoThey 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.
Perhaps LineageOS could help. Or GrapheneOS.
I’ll be watching to see how Graphene handles this, as Graphene is currently my daily driver.
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.