How to pass --trusted-host or get brew to use corporate certificate passed to pip via $PIP_CERT? #5169
Replies: 3 comments 4 replies
-
Can you try the following? From the caveats in the output of
|
Beta Was this translation helpful? Give feedback.
-
Update, for what it's worth, I ran with --keep-tmp and --debug so that the temp directories remained and it paused upon failing. Then I opened up a new terminal so I could run the exact commands it failed on (seemed like trying to pull in setuptools as part of argcomplete?), and it worked fine. So, still not clear what exactly the issue is when doing that command as part of a dependency vs running it directly? What user does brew run as, and would that see $PIP_CERT? |
Beta Was this translation helpful? Give feedback.
-
I have the same issue which is driving me crazy. I'm trying to upgrade glib. For sure, the problem is with my ssl-intercepting proxy. I just can't find the right certificate path to add the proxy cert.
I'm trying to modify the formula, but also no success yet.
|
Beta Was this translation helpful? Give feedback.
-
Output of
brew config
Output of
brew doctor
Description of issue
Issue #15764 is exactly what I'm running into, but after discussion of alternative certs, the discussion went stale.
I was trying to
brew install qmk/qmk/qmk
, and it fails at this point:As stated in the linked issue, it has something to do with certificates and the corporate firewall. I've run into this before, and one can use something like
--trusted-host
(see this SO post), and my company provided a cert bundle, which I have pip pointed to usingPIP_CERT=/path/to/bundle.pem
in my~/.zshrc
.I'm wondering if anyone can suggest how to pass arguments or this bundle to pip when it's building dependencies like this? Or kindly let me know I don't understand the problem and it's something else.
Beta Was this translation helpful? Give feedback.
All reactions