You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 13, 2021. It is now read-only.
In tls.py we use SSLContext.set_default_verify_paths() to get the system certificate bundle. This works fine on my OS X development box, but leads to cert verification errors on Windows.
Options are either to use a Windows-specific version as well that we know will work, or to start bundling requests' CAcerts.
The text was updated successfully, but these errors were encountered:
Ok, I've fixed this by using the same certificate package as Requests uses. @kennethreitz, are you ok with cross-project use like this? I'm grabbing it from your CI server. If you aren't happy, let me know and I'll work out an alternative.
By all means! Ideally, I'd like to have a more proper domain/project setup for this. I'll get around to that eventually in conjunction with @dstufft :)
In the meantime, just grab away, or depend on certifi :)
@kennethreitz Awesome, thanks! =) If you ever need a hand sorting that out, I've got a barely-used Digital Ocean server that I'm happy to devote to the cause.
In
tls.py
we useSSLContext.set_default_verify_paths()
to get the system certificate bundle. This works fine on my OS X development box, but leads to cert verification errors on Windows.Options are either to use a Windows-specific version as well that we know will work, or to start bundling requests' CAcerts.
The text was updated successfully, but these errors were encountered: