4 ms·
This sounds nice for security, hell for some developers but: What happens in 2-3 years when this version of Android is abandoned? You pray the hardcoded certif
by nottorp 3y ago
This sounds nice for security, hell for some developers but:
What happens in 2-3 years when this version of Android is abandoned? You pray the hardcoded certificates will last you a couple more years?
- idiotsecant 3y agoObjective achieved : consumer buys new phone.
- arusahni 3y agoThey're updatable via Google Play starting with 14, so not tied to OS updates.
- nottorp 3y agoBut google will abandon this Android version fairly soon as we all know… what Google Play updates in 6 years?
- arusahni 3y agoGoogle already guarantees Pixel security updates for 5 years, so I'd say that's at least the baseline. When Google removed Play Services support for the 4.x series they were 9 years old at that point.
- nottorp 3y agoGoogle and guarantees in the same sentence? https://arstechnica.com/gadgets/2023/08/google-kills-two-year-pixel-pass-subscription-after-just-22-months/ https://arstechnica.com/gadgets/2023/08/google-kills-two-yea... Random example that even has pixel in it. Not to mention the other randomly canceled services.
- arusahni 3y ago/shrug you do you.
- jeroenhd 3y agoGoogle still updates the built-in for Android 7. They don't really abandon device support for old OS versions like iOS tends to. The current situation is that the CA bundle doesn't receive any updates from Google. If your manufacturer repackages their CA bundle and still updates your device, you'll receive a new CA bundle, but I don't believe this is guaranteed. Furthermore, if you're still running Android 14 after six years, your issue is with the manufacturer of your device. The latest version of the CA bundle will still work of course, but you should really be at least four or five Android versions higher at that point.
- looperhacks 3y agoMy wife just had to replace her phone because of that. Apps generally don't accept user certificates and the first apps stopped working because Google cloud (or something related) updated to a newer certificate
- jakub_g 3y agoIt's been a long known issue [0] that cert providers had to account for, but apparently not anymore [1] from Android 14 > Android 14 makes root certificates updatable via Google Play > Android's root store used to require an OTA update to add or remove root certificates. That won't be the case in Android 14. TIL there's a workaround though [0]: > If you use Android 7.0 or earlier, you may need to take action to ensure you can still access websites secured by Let’s Encrypt certificates. We recommend installing and using Firefox Mobile, which uses its own trust store instead of the Android OS trust store, and therefore trusts ISRG Root X1. [0] https://letsencrypt.org/2023/07/10/cross-sign-expiration.html https://letsencrypt.org/2023/07/10/cross-sign-expiration.htm... [1] https://www.xda-developers.com/android-14-root-certificates-updatable/ https://www.xda-developers.com/android-14-root-certificates-...
- cosmojg 3y agoGood ol' Firefox, keeping up its reputation as the only user-respecting major browser.
- izacus 3y agoCertificates are an APEX module now (which is the crux of authors complaints actually), which means they're updated out of band by Play Services and don't need an OS update from OEM.
- jmholla 3y ago> What happens in 2-3 years when this version of Android is abandoned? I had to install a Let's Encrypt certificate to get my self-hosted password manager working because Google's updates are missing an intermediate certificate Let's Encrypt uses. This is not a hypothetical down the road issue but an issue present right now. Why should Google be the final arbiter of who I trust? They clearly have their gaps. And let's not even get started on the existing approved certificate providers that you shouldn't really be trusting since they've been shown to provide certificates to people and organizations that shouldn't have them.