UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.7 Safari/537.36
Steps to reproduce the problem:
1. Setup charles to inspect the https traffic.
2. Install the charles cert to the phone.
3. Use addPublicKeyPins API to pin the cert.
4. See the traffic can still be intercepted by chareles.
What is the expected behavior?
Cronet fail the request because the local installed cert doesn't match the pin.
What went wrong?
Cronet should not skip local certificates in public key pin check.
Did this work before? N/A
Chrome version: 51.0.2704.7 Channel: n/a
OS Version: OS X 10.11.4
Flash Version: Shockwave Flash 21.0 r0
I saw this behavior was mentioned in 522275's discussion but not implemented in the final api. Can we revisit this? We are worried that third party app could trick the user to install their cert and perform mitm attack.
Comment 1 by ashej...@chromium.org
, Apr 27 2016Labels: Te-NeedsFurtherTriage