4 ms·
This is a pretty annoying move for anyone who has their own CA they use to sign internal domains. I wonder if they will also have Chrome not trust them...
by ingenium 10y ago
This is a pretty annoying move for anyone who has their own CA they use to sign internal domains. I wonder if they will also have Chrome not trust them...
- andrewguenther 10y agoKeep in mind, this specifically affects apps. Not necessarily Chrome, which I would guess is going to use the Trust API to allow them. So unless you have custom apps that access internal domains, then you shouldn't be impacted at all.
- kuschku 10y agoAnd how can I force all apps to accept it? I’ll have to end up rooting every device. This will just mean that even more will be running rooted, reducing security.
- Natanael_L 10y agoRoot and Xposed, yes. That's probably going to be the easiest solution. Root doesn't inherently reduce security - it only adds as much target surface as you chose to add. Adding root services with bugs is dangerous, but one-off tasks with secure code and a secure root manager isn't a problem.
- blastrat 10y agoif you have custom apps, this announcement tell you how set your apps to trust your own CA certs.