since the last update every application on the phone do not trust us on CA anymore. On webbrowser for example i get this default error: “Security connection unknown certificate”. The certificates are installed and visible in the system-settings.
What have I already tried?
delete and install the CA again
manual install of CA’s over the webbrowser
testet with firefox, and the build in chrome
Testet with other apps, same problem, self-installed certificates are no longer trusted
reboots beween processes
testet on us two fairphones
Can anyone help me? Are the CA’s to be installed differently? Has anything changed?
/e/ supports a lot of devices, and some get updates for different Android versions simultaneously, so depending on the device even with a date it might not be clear what Android version the update was for, then there are different release channels you could be on …
In short: What exactly does it say in Settings - About phone - Android version - /e/ version?
What exactly does it say in Settings - About phone - Android version (you can tap on this to get further) - /e/ version?
For me it currently says 0.17-q-20210529117214-dev-FP3 there, so it includes the Android version “q” for 10, the update release channel “dev” and the device “FP3”. All the necessary info in one place (yes, it would be better they would display this as the version everywhere consistently).
Update: Tested on many webbbrowsers and i installed the certs on 2 ways. Directly from the webbrowser and local. Same result.
The new mainproblem is that we have now deepinspection also in the office and at the customers as an obligation. So this time the mobilephone is not useable online in that networks. That is definitely not fun.
So i’ve reseted completly one of the fairphones, but the problem remains.
Doesn’t anyone use e/os with their own certificate authority?
Hello all, so now a time later, and latest update, the issue exist. Since I don’t necessarily want to reset my devices here again… if someone has a test device available to test the certificate store would be very helpful.
Ok, i reseted my own phone. CA did’nt work. So e/OS is not usable for business. I will have to recommend my company to buy Google phones again. Too bad.
you can still use a user-provided root-ca, but depending on API level an app targets, the App needs to opt-in to trust user-supplied root-CAs on the device
User-added CAs
[…]. Android Nougat changes how applications interact with user- and admin-supplied CAs. By default, apps that target API level 24 will—by design—not honor such CAs unless the app explicitly opts in. […]
Custom trust anchors: Customize which Certificate Authorities (CA) are trusted for an app’s secure connections. For example, trusting particular self-signed certificates or restricting the set of public CAs that the app trusts.
I gave this a try, it’s a bit cumbersome but Firefox has a hidden option for this, and accepted a certificate signed by my own root-ca-cert.
here is the number: