[dijit]

Used to work at Ubisoft and they had this same policy, they used an authenticated http proxy, so you either expose your entire SSO credentials to your environment (HTTP_PROXY=http://user:password@proxy:3128) or you don't get access to the internet for all your console applications.

Even then, if you were using certificate pinning, it wouldn't work as the HTTP proxy would serve a "are you sure you want to continue" HTML page, which is of course not expected.

SSH is out of the question.

it's amazing what "simple" things break; like kubectl, gcloud, go get.

So frustrating. Countless development hours lost to bypasses.