4 ms·
Note that this only counts for certificates in the system store. As far as I know, certificates stores in the user store (the one you use when you import a cert
by jeroenhd 5y ago
Note that this only counts for certificates in the system store. As far as I know, certificates stores in the user store (the one you use when you import a certificate through the UI) will override this requirement and work just fine.
The underlying problem is that apps stopped trusting user certificates by default in Android 7 so security researchers have had to root their devices and store certs in the system store.
Theoretically this should work if you can manage to get the certificate in both the system and the user store, though I don't think you can do that.
I'm thinking something like this: you add the root certificate to your system store so most applications will trust it; then you create an intermediate certificate authority for your MitM-ing (which you should probably do anyway if you're doing this long term) and import that certificate into the user store.
Hopefully, that way Chrome will see the user store intermediate certificate and validate it using the non-CT algorithm. I haven't tried it, though!
Note that for MitM-ing Firefox, you need to access the secret dev settings (go to about, hit the Firefox logo seven times to enable them) and enable loading user store certificates.
- justsomehnguy 5y ago> The underlying problem is that apps stopped trusting user certificates by default in Android 7 The other casualty were the people who use their own CAs. It took me some time to grok what the problem with some apps (which didn't want to connect) wasn't in my server configuration, but the certs they served. TLS-ALPN somewhat alleviates this problem, but still requires to have some real presence on the net.
- Melatonic 5y agoThis is the real answer. While I of course support hardening security I have to think that Google has other motivations by introducing these restrictions on the system cert store. There are legitimate use cases where you want want to MITM yourself (or your employer). This combined with cert pinning combined with use of encrypted DNS (which is definitely not a bad thing in it of itself) means that Google is going to keep having access to useful tracking data.
- spacexsucks 5y agoAgreed. This is just another prevention measure to line their pockets
- asddubs 5y agowasn't chrome going to add it's own certificate store? whatever happened to that?