It's a bit more complicated than just wrapping urllib2 calls. The failure cases actaully need to be handled properly, and the user notified/presented with options to approve certs somehow, and this report specifically seems to be about the gwibber-accounts part of the code, when adding an account.
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gwibber in Ubuntu. https://bugs.launchpad.net/bugs/705363 Title: gwibber bypasses certificate checking when providing the login/password for OAuth Status in Gwibber: New Status in “gwibber” package in Ubuntu: Confirmed Status in “gwibber” package in Debian: Confirmed Bug description: Someone reported this in Debian: http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=608724 identi.ca had (mistakenly) installed an SSL certificate not recognized by the installed CA, yet the user has been presented with the OAuth login screen even if that https connection could not be authentified. To manage notifications about this bug go to: https://bugs.launchpad.net/gwibber/+bug/705363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
