updated protocol version to tls

[formigarafa]

this will solve the issues with server not responding to sslv3 due to bug found in the protocol (POODLE)

[ab]

Pinning to TLSv1_2 probably isn't what you want to do here, since that will prevent clients from connecting to any servers that use a protocol other than TLS 1.2 (so no TLS 1.0, nor 1.1, nor future 1.3).

If you set any default value at all, it should probably be the confusingly named SSLv23, which is code for basically any TLS protocol version.

[treeder]

Yep, we found that out the hard way. :) Already switched to SSLv23 in
1.8.1.

On Mon Oct 27 2014 at 11:04:19 AM Andy Brody notifications@github.com
wrote:

Pinning to TLSv1_2 probably isn't what you want to do here, since that
will prevent clients from connecting to any servers that use a protocol
other than TLS 1.2 (so no TLS 1.0, nor 1.1, nor future 1.3).

If you set any default value at all, it should probably be the confusingly
named SSLv23, which is code for basically any TLS protocol version.

—
Reply to this email directly or view it on GitHub
#3 (comment).