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.
Fully 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.
This 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.
The day windows takes away my administrator power is the day I switch to Linux
This guide, in the third section at the bottom talks about using KeyTool to boot into UEFI and is how you get around this issue: https://wiki.gentoo.org/wiki/User:Sakaki/Sakaki's_EFI_Install_Guide/Configuring_Secure_Boot
Firmware bootkit vulnerabilities are one of the largest attack surfaces available right now. There are ways to deal with this, it is just added complexity. The intellectual barrier is becoming harder. Secure boot is important though.
I don’t think it should be illegal, there are people who are not technically capable and can give permissions when they shouldn’t. I believe there should also be an an option where as a power user you are given those controls again because you have the technical understanding of what you are doing.
Correct me if I’m wrong, but I have a work profile with a cert authority installed in a work profile managed by Intune. If I update to Android 14, I’ll lose this?
Unless it’s a fully managed device (different to a work profile - this has to be configured when the device first boots, it’s for phones that are fully corporately owned & managed) then I think that has to be acting as a user-level CA certificate (trusted only by apps who opt in to trust it, which notably includes Chrome) not a system-level CA certificate (trusted by all apps by default). That will keep working just fine.
I 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.
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.
