Native TLS option fails on corporate laptop. #4077
Comments
|
As far as I can tell, we didn't change anything here from 0.2.5 to 0.2.7. We did upgrade some dependencies. But |
|
I will investigate further and report back. |
|
Thanks. |
|
Update: I was trying different versions and noted that For the previous several versions, I could not run What I observe is that for the self-update operation, version 0.2.9 changed behavior and is able to use my system certificate. However, the same is not true for |
|
So, 0.2.9 also works if my index source is pypi.org rather than our proprietary server. But it's not a real certificate issue on our server because uv is perfectly happy to accept those certificates if I run on the same machine using linux on WSL. |
|
I'd recommend taking a look at these similar issues
The general theme here is that we don't actually implement certificate loading so we're unlikely to be able to help you. Here's a portion of one of my previous comments:
|
|
You could also bisect the regression to a specific commit on uv, which would be very helpful for investigating the source of the issue. |
|
I will try to identify a specific commit. Also, Schannel works fine for git-for-windows and for mamba-forge. I will take a look at the upstream rust-native-certs repo for related issues. Thank you! |
|
@zanieb, this issue may be the culprit: rustls/rustls-native-certs#22 Coupled with the upstream bug in loading the SSL certificate file (I also tried that), I seem to be blocked, but it looks like the upstream TLS package will resolve this in the long run. I will also try using the SSL certificate variable again. Because that may be needed. |
|
I found more confusion when comparing running in Powershell 7 vs git bash. In git bash with SSL_CERT_FILE defined, |
|
Thank you so much for doing this investigation! |
|
Bumping since the devs of |
|
@gdebrun2 Can you open a new specific issue with a request instead of bumping? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Previous versions, prior to 0.2.5 I think, worked on my corporate laptop that includes the Cisco Umbrella proxy. The current version 0.2.7 (and 0.2.6 and 0.2.5) appears to have broken support for native TLS, the
--native-tlsoption does nothing. The issue is in the Windows environment.uvdoes still work on linux in WSL2 as long as I'm not connected to the corporate firewall.Note that the environment variable UV_INDEX_URL is set to point to a JFrog pypi mirror that includes proprietary packages. I used to have the variable set for native TLS, but I removed it when it stopped working sometime around version 0.2.5 (it could have been an earlier version).
The text was updated successfully, but these errors were encountered: