This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients alex, benjamin.peterson, christian.heimes, doko, dstufft, giampaolo.rodola, janssen, kroeckx, lemburg, ned.deily, pitrou, python-dev, vstinner
Date 2014-12-12.13:23:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwYfg88Ew95SUx5j_TqG8pc0EfqXChZbceGUMuLi6ta-hg@mail.gmail.com>
In-reply-to <1418390199.99.0.697604840555.issue22935@psf.upfronthosting.co.za>
Content
> Any of the other options such as PROTOCOL_TLSv1 will fix the protocol version to that one protocol version, whereas PROTOCOL_SSLv23 means to use any protocol starting with SSLv2. In the context options you can then disable SSLv2 and SSLv3 to e.g. have the connection use TLS 1.0 or later.

get_server_certificate() uses _create_unverified_context() (In Python
2.7, 3.4 & 3.5) which explicitly disable SSLv2 and SSLv3. I still have
trouble to understand which protocol will be negociated. We use SSLv3
and disable SSLv3, so the server can only use SSLv23. Am I right?
https://docs.python.org/dev/library/ssl.html#ssl.wrap_socket
History
Date User Action Args
2014-12-12 13:23:26vstinnersetrecipients: + vstinner, lemburg, doko, janssen, pitrou, giampaolo.rodola, christian.heimes, benjamin.peterson, ned.deily, alex, python-dev, dstufft, kroeckx
2014-12-12 13:23:26vstinnerlinkissue22935 messages
2014-12-12 13:23:26vstinnercreate