Let’s Encrypt have announced that they will change the root certificate for newly issued SSL certificates on the 29th of September, 2020. This is because their present root certificate will expire in a few years. As their certificates have a lifetime of 90 days, the last ones with the old root will be gone by the 28th of December, 2020.
This will mean that web services using Let’s Encrypt for encryption will no longer be reachable on older devices. It will affect the Android browser, Google Chrome, and other apps for online services if the server/website which it is contacting has a Let’s Encrypt certificate. This will affect Android below 7.1.1, which means all FP1, and any FP2’s that are still on Android 5/6.
Note that many of the affected websites and apps may already have stopped working before as a result of the end of support for TLS 1.0/1.1 by many websites in the past few years.
The good news: Firefox is, again, not affected. It uses its own certificate store on all operating systems. I don’t know the situation for the Firefox forks used by many Fairphoners, but there’s a good chance that they’ll work too as they were not affected either when TLS 1.0/1.1 got dropped.
If your favourite app has a browser-based version, you will probably still be able to use Firefox (or a derivative of it) to connect to it.
Hi siltaar,
I am still on FP1U
And I often face websites not opening (“error”).
Do I understand it right that I can install [quote=“siltaar, post:3, topic:62089”]
Firefox Mobile or IceCat Mobile
[/quote] and probably get rid of these (certificate?) errors?
However, I tried to install these apps on my FP1 but I didn’t find them in (my) Play Store.
KR Michael
I should add here: IceCat displays a blank page on a few sites because it doesn’t run JavaScript files without a free license. Would follow Lidwien’s suggestion if usability rather than FOSS software is your main goal - although I haven’t tried Lightning to be honest. More importantly, I can’t find whether it implements its own certificate store.
(I also don’t have an FP1, but a different phone of similar age has passed between family members in recent years. I know that it currently has Opera installed on it, which didn’t lead to complaints yet.)
Otherwise, if you activate the F-Droid archive repo in F-Droid, you can download the 68.12.0 version (the last one before the fenix upgrade), it runs on android 4.1+. That’s the version I run on my FP2 because I currently don’t like the last one (probably too rushed) and it runs perfectly fine.
For anyone who is still worried, I think there is another solution as well:
As far as I remember, the systems certificate store isn’t a black-box at all. The user is able to install (and trust) any new certificate as he pleases or as well deactivate already installed certificates.
On Android 10 the menu entries for these actions are located at “Settings > Security > Encryption and Credentials”. I do not know the path for older Android versions, but I am pretty sure, these options are present since the first Android versions.
Given basic technical understanding, a user would be able to install the new Root certificate, once downloaded. LetsEncrypt publishes their current Root Certificate on their website to download, so it is reasonable that they’ll do so with the new one too.
Yet, I haven’t tried this myself, so I might miss some catch here and this obviously opens a possibility for scammers to mislead unaware users too. Hence, I think the announced extended compatibility are good news.
The catch here is that the SSL engine of Android 4.2 also does not support TLS 1.2 or 1.3, so you still need a browser that comes with a built-in SSL engine to access many sites (e.g. a Firefox derivative), regardless of the certificate. This has already been the case for over a year, however, so FP1 users have already adjusted to that.
Firefox also bundles a more recent store so it solves both problems if you find a version compatible with Android 4.2. Other browsers may only solve one of the two problems.
