13:54 <ms11> hi. wanted to ask if anyone from rubygems was working to address the connectivity/TLS issues that many have reported...

13:54 <ms11> http://help.rubygems.org/discussions/problems/31156-problems-connecting-to-rubygems

13:54 <ms11> http://help.rubygems.org/discussions/problems/31227-issue-with-cdn-certificate

13:54 <ms11> http://help.rubygems.org/discussions/problems/31211-problem-downloading-rubygems-dependencies

14:06 <ms11> $ curl -v https://api.rubygems.org * Rebuilt URL to: https://api.rubygems.org/ * Trying 151.101.194.2... * Connected to api.rubygems.org (151.101.194.2) port 443 (#0) * found 148 certificates in /etc/ssl/certs/ca-certificates.crt * found 592 certificates in /etc/ssl/certs * ALPN, offering http/1.1 * gnutls_handshake() failed: Error in the push function. * Closing connection 0 curl: (35) gnutls_handshake() failed: Error in the push

14:06 <ms11> * Closing connection 0 curl: (35) gnutls_handshake() failed: Error in the push function.

14:16 <ms11> i'm also talking with #fastly support. perhaps they jumped the gun on their tls 1.0/1.1 deprecation, and rubygems haven't yet switched over to tls 1.2?