Re:Android: I don't need your permission
by joshfraser on Tuesday December 16, 2014 @04:29PM
(#8759638)
I assume you'd set up a custom CA on your proxy so you can spy on the https traffic. I'd be suspicious if I saw large blogs of data that had been encrypted in the application instead of at the network layer.
[ Parent
| on HN ]
Re:Android: I don't need your permission
by Ded7xSEoPKYNsDd on Tuesday December 16, 2014 @04:48PM
(#8759767)
But then best practices say you should be doing cert pinning. That will block your CA.
Although for most apps modifying that check to look for another cert is probably not too hard. (But of course if the app is obfuscated and does integrity checks on itself, it can get arbitrarily complicated.)
Re:Android: I don't need your permission
by voltagex_ on Tuesday December 16, 2014 @05:30PM
(#8760001)
I visit sites with cert pinning at $EMPLOYER. $EMPLOYER runs a very expensive solution from Blue Coat which includes a MITM CA - no issues intercepting anything here. Amusingly, this meant the proxy itself was vulnerable to Heartblead while the client machines were not.
Re:Android: I don't need your permission
by MichaelGG on Tuesday December 16, 2014 @09:29PM
(#8760785)
Browsers know this is s common downside to corp environments and excuse them if the proxy cert is installed. Arbitrary apps don't have to follow that.
Re:Android: I don't need your permission
by btgeekboy on Tuesday December 16, 2014 @10:56PM
(#8761006)
The only foolproof way to get around this is to hardcode the certificate into the application itself, or at least the intermediate chain. Otherwise, you could have always intercepted the first request and made that the certificate of record.