SSL certificate verify failed - #56
Conversation
|
The problem is that httplib2 has recently started requiring SSL certs to be verified, but the list of CAs that it is honoring is not complete. Options at this point are to pip httplib2 0.6.0 (you can do this by removing the installed one and installing the old version), or making a patch to httplib2 to give it a fuller list of CAs. You can add to it here: |
|
I think I'd like to see an interim fix pushed out to fix this, as it will affect people deploying with Options:
Any opinions? I've just switched to option 3 for our packages, but I'm not particularly tied to the decision. Thanks, James |
As unfortunate as bundling may be, we may as well take advantage of it.
|
The commits attached are for a simple, only lightly tested, option 3. Removes support for httplib2 <0.7, but it would be easy to support both if needed. |
|
I suppose it doesn't matter in our case since we're only talking to GitHub, but I'll point out that supplying a ca_file to Httplib2 is not additive; that is, only DigiCert certificates will be trusted after this change. |
Require httplib2 0.7 (which added SSL cert verification) and trust DigiCert (only) which is used by Github.
|
By the way, for posterity, the DigiCert root included in this commit can be verified here: |
The quickstart example in the documentation fails with
and I cannot find any information on what to do in either the error message nor the documentation.