Comment 7 for bug 729185
Revision history for this message
| Olaf Meeuwissen (olaf.meeuwissen) wrote | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Re #5, we've tested with the fixed code and getting the GPG fingerprint worked fine for us.
Not familiar with the python-pycurl code, I've one little question. The verified_https.py code seemed aimed at adding hostname validation, something HTTPSConnection didn't do. Assuming that was done on purpose, I guess the replacement code should do the same. Does pycurl do the validation? If yes, then I think the fix is OK. If no, then it might need a bit more work.
Now that getting the GPG fingerprint works it time to make GPG proxy aware, see #733023 ;-)