Android 14 blocks all modification of system certificates, even as root
Android 14 blocks all modification of system certificates, even as root
When Android was initially announced in 2007 by the Open Handset Alliance (headed by Google) their flagship project was billed as an "open…
Treating their users like idiots and more control. Why can’t this be editable but just under Developer Mode?
I’m just waiting for sideloading to be blocked due to “security.”
FFS, even iOS lets you install certificate profiles
30Certificate profiles are ok, you just install them as user certs (as it does for apple), this limitation only concerns root certs.
1
The headline reads like an ad for GrapheneOS and LineageOS.
27Anything google does is an ad for grapheme and lineage tbh
12Tough, but fair.
7
Permanently Deleted
27Previously any user could modify these certs directly, even on vanilla OS images from Google themselves, without installing Magisk or any tools at all, just by writing to disk. Right now, that's widely used and included in the setup guides for lots & lots of tools. All of that will start breaking for users when Android 14 arrives.
I totally agree it is possible to work around this restriction, but it's going to be significantly more complicated, and those changes will only be required because the OS used to let you read & write these files all by yourself, and now it doesn't.
I don't think Android should move further in a direction where it's impossible to directly control anything unless you install a 3rd party modification to the root daemon. That's not a good result. These are important settings and the OS itself should allow you to control them (behind reasonable safeguards & warnings, but still).
9
It's an interesting write up. But I don't think it's valid for one reason, company devices often require a company certificate to be fully trusted so that the company firewall can inspect all traffic transiting it.
So there must be a mechanism that allows corporately managed Android devices to adhere to corporate firewall policies.
Not just corporate, there's some countries that require you to install their certificate before you can use the internet.
23Fully managed corporate devices can do this, there's a separate mechanism for that: https://developers.google.com/android/work/requirements/fully-managed-device
This only works when the corporation fully manages the device though - not for normal work profiles. It's only possible to enable that setup when the device OS is initially installed, and the resulting device is controlled 100% by an IT administrator. It's not something you can do for your own device, and even for small companies it's quite complicated and expensive.
15This is exactly what's happening with Windows, too. Unless you're a business with an Enterprise version, control is being ripped away from you. We're getting to the place now where individuals are no longer permitted to be admins of their own devices unless they're corporations that pay for the privilege. I said it years ago when they took GroupPolicy out of Home edition: it was normalizing admin control as a premium feature, that one day average people will be priced out of.
Combine that with a lot of the other environment integrity/hardware attestation bullshit Google and Microsoft are pushing more and more, so that even if you do manage to wrangle admin control back from them, you can be prevented from participating in the larger internet ecosystem for having the audacity to do so. Even Linux won't be a meaningful retreat when the largest and most popular websites and apps collectively decide you have to use what is effectively a corporate approved kiosk to access them.
This shit should be illegal.
15I agree it's a pain in the butt. Using an open source MDM, EMM gives you the ability to configure your device your way.
https://github.com/h-mdm like this
It shouldn't be required though. Totally agreed.
4
I'd imagine in both cases you'd have to play nicely with google for them to push your certificates to the devices for you and/or give you tools to do so.
IE still available for those with power/money, but any regular citizen can go hump a cactus.
3There's far too many corporations out there for that to be the case. It would cost them far more in managing that controlled access than they could possibly gain from whatever control they're trying to exert here
4
I kinda understand why they do this. Android has slowly been going the route to be only for dummies that shouldn't be able to touch anything. And most device makers are completely fine with it, evidently.
What's needed is a really decent alternative OS, or several, with widespread support across devices.
Yea there's Graphene, but in terms of devices, do you want this year's Google, last year's Google, or an overpriced recycled phone? And in terms of firmware the situation is even more difficult.
Even 10 years later I'm still mad at Firefox for letting go of their FF OS.
13FirefoxOS lives on as KaiOS
3
I feel like 12 was probably the last decent one. Maybe even 11.
4rip AdGuard
2Self host time
3I meant https filtering
1
Besides the listed examples from the article, what would be the impact for normal to even hobbyist root users? It seems like this is a good idea to prevent modification of legit certs and allowing certs to be updated remotely.
As touched on above: if you're configuring your own system CA certificates on Android right now for debugging, reverse engineering, testing or research, that option is going away in Android 14, and presumably all future versions too.
1