Regression: Unable to bypass ssl verification any more for corp firewall

[ericanderson]

• VSCode Version: 1.5
• OS Version: 10.11.6

Steps to Reproduce:

1. Install a transparent man-in-the-middle firewall with a self signed cert and be sure that all traffic is being intercepted.
2. Install VSCode 1.4.
3. Notice that VSCode can't update extensions due to MITM.
4. Set http.proxyStrictSSL=false
5. Notice that VSCode can now update extensions or search extensions, etc.
6. Upgrade to 1.5
7. Notice that VSCode can no longer speak to the internet when trying to search for an extension

[mderriey]

The same issue happens to me after updating to 1.5. Using Windows 7 SP1.

[joaomoreno]

@ericanderson Can you show me how I can do step 1?

Install a transparent man-in-the-middle firewall with a self signed cert and be sure that all traffic is being intercepted.

This has been the major problem in fixing proxy issues: I don't know how to reproduce all these scenarios.

[ghost]

@joaomoreno The same issue is reproduced with http/https proxies with self-signed certificates, I also reproduce this issue in our corporate network since the update.

[joaomoreno]

Awesome, was able to reproduce this using Charles. Will definitely buy this to keep the proxy issues in control.

[joaomoreno]

Found the issue, pushed to master. Will try to get it into a recovery build asap.

[mderriey]

Thanks for being so responsive! Keep up the good work!

[darron-haworth]

Thank you for the update! 👍

[seanmcbreen]

While we wait for a broad update you can use Insiders to work around this...
http://code.visualstudio.com/insiders

[joaomoreno]

@seanmcbreen The latest insiders doesn't have the fix yet, since last build happened Friday morning (CET). I'm triggering new insider builds and releasing them, so people get it.

[joaomoreno]

Verification: use Charles to proxy SSL requests to/from https://marketplace.visualstudio.com/. Set up Code to use Charles as a proxy and setstrictSSLtofalse`.

[sbromberger]

Just wanted to say - bravo and many thanks for the quick fix!! 👍

Oh yeah - confirmed fixed on OSX 10.11.6.

[mrichman]

Confirm fixed on Windows 10.

[mderriey]

Thanks for fixing this so quickly and getting it out in a matter of days!

[joaomoreno]

Thanks for the confirmation guys.