4 ms·
this ignores user trust. now the closed source application is impervious to mim attacks or bad CA operators but the user also have no way to validate the traff
by gcb0 9y ago
this ignores user trust.
now the closed source application is impervious to mim attacks or bad CA operators but the user also have no way to validate the traffic comming out of their very own device.
generic is good sometimes. and the generic solution already account for generic user/app local certificates just fine. no need to hide an extra one that can't be verified/update inside the app. that's kinda of an asshole move.
- tptacek 9y agoThis doesn't make sense. Do you have the private key for Facebook's Digicert-signed certificate? No, you don't. So what difference does it make whether you get certificate trust from Digicert or from an anchor installed along with your mobile app?
- saurik 9y ago... because you essentially are always allowed to install your own custom root certificate when people use the system SSL support, even on iOS? (FWIW, I also feel like the implied solution here is wrong, but your analysis is worse.)
- tptacek 9y agoWhat difference does that make? It's also annoying to test applications that don't honor system proxy settings. And?