-
Notifications
You must be signed in to change notification settings - Fork 7
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
Add command line flag to bypass SSL check #70
Comments
To be clear, you're running this inside an Ubuntu Docker container within MacOS? |
yes, so to give you the full picture, I'm using my work laptop which is a mac m1 chip, I use docker as a dev environment (basically as a drop in replacement of a Linux VM, as I use vim as a code editor I don't need a GUI) |
and I'm trying to use your little tool in combination with this other open source project: |
You still haven't posted the error for that. All of those deletions are with The way you're using this isn't really intended or supported, although I'd be happy to try to get it working. This is a docker/macos issue, not a zeal-cli issue. That said, I'm going to recategorize this issue as a feature request and consider adding a way to bypass the SSL check. |
Most likely this will happen after the release of major version 2.0.0 in a minor version. |
thanks so much for the consideration. I'm not sure this is a macos / docker issue. I think it's more of a SSL certificate handling issue? are you using SLL certificates as well on your machine? I suspect a lot of company computers are behind some sort of proxy or firewall that require handling of such certificates. |
I was looking at the error wrong (I've dealt with similar errors before on MacOS and I assumed thats what it was). It's an issue with your corporate network using a self-signed SSL certificate somewhere inline (my guess is that your corporate proxy uses one). It's still an issue with your setup, just in a different place then I thought. Zeal-CLI always uses SSL, including verifying certificates. |
@darzok0914 this is supported but you are not including self-signed certificates into Docker container. The proper way of handling this is to copy them from system and use "REQUESTS_CA_BUNDLE" env variable to point to it. By default, requests use Mozilla list of trusted CA (widely used in open source) - https://pypi.org/project/certifi/, which for sure won't have local one. This is why you have to use variable to pass path to your local CA bundle that has all certificates that are known, and among these, there should be self-signed from corporation. |
Describe the Bug
When I try to install a docset for cpp I have a SLL certificate error.
Expected Behaviour
Would it be possible to pass some cmd line argument (or a config file?) to either disable the ssl certificate check or pass the path to that certificate?
https://www.geeksforgeeks.org/ssl-certificate-verification-python-requests/
Steps to Reproduce the Bug
Version
1.2.0
OS
Additional Context
I am using ubuntu 20.04 on arm64 (docker dev env on mac m1 chip)
The text was updated successfully, but these errors were encountered: