Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

exclude GIT_SSL_NO_VERIFY env variable from getting stripped #1293

Merged
merged 1 commit into from Jan 21, 2020

Conversation

@schiermike
Copy link
Contributor

@schiermike schiermike commented Jan 21, 2020

Can this change please get merged? We sit behind a proxy that messes with certificates...

@asottile
Copy link
Member

@asottile asottile commented Jan 21, 2020

that's actually kinda terrifying -- doesn't this variable expose you to all sorts of malicious MITM?

I'm looking into why windows CI is failing -- I suspect a bad azure pipelines release :(

@schiermike
Copy link
Contributor Author

@schiermike schiermike commented Jan 21, 2020

Yeah, a bit yes. The proxy itself is pretty restricting and only allows connections to a handful of public domains such as github.com - and it does verify certs. So it's only a matter of trusting the path to the proxy inside the company network ...

Copy link
Member

@asottile asottile left a comment

change seems fine (though scary!), I'll merge after fixing CI

@asottile asottile force-pushed the schiermike:master branch from 4c5867f to d9800ad Jan 21, 2020
@asottile asottile merged commit 627c9eb into pre-commit:master Jan 21, 2020
1 check passed
1 check passed
pre-commit.pre-commit #20200121.8 succeeded
Details
@asottile
Copy link
Member

@asottile asottile commented Jan 29, 2020

this has been released as part of v2.0.0 -- thanks again for the patch!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants
You can’t perform that action at this time.