Hi, I dug in a little deeper, rebuilt the libcurl3-gnutls package, and found what I believe to be the culprit:
https://github.com/bagder/curl/commit/cbf4961bf3e42d88f6489f981efd509faa86f501#L0L219 In previous editions of libcurl-gnutls, the line of gtls.c in question reads: what = Curl_socket_ready(readfd, writefd, nonblocking?0:(int)timeout_ms); Now, it reads: what = Curl_socket_ready(readfd, writefd, nonblocking?0:(int)timeout_ms); The effect is that where previously, the the SSL handshake would block "as long as it took" to complete the handshake. Now, it only waits for one second. If your connection is fast enough, it works fine. But if you're on a crappy high-latency CDMA modem on a state-run telecom in Africa, you get "SSL timeouts". The commit also links to this bug report: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594150 It seems like this change was made because SSL connection timeouts were covering other bugs. Note also that if you rebuild the curl package, you can witness this failure "by hand". ethan@jonah-hex:~/software/curl-7.21.3$ ./debian/build-gnutls/src/curl https://github.com curl: (28) SSL connection timeout at 297679 I'm not completely sure about what the fix is here. I am going to report the bug upstream and see what happens. Ethan ** Bug watch added: Debian Bug tracker #594150 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594150 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/762783 Title: Gwibber Not Updating.. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
