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 gvanrossum
Recipients geertj, giampaolo.rodola, gvanrossum, pitrou, sbt, vstinner, yselivanov
Date 2015-01-02.04:21:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Oh, I think I understand how this could help STARTTLS. Glyph once explained it to me. STARTTLS takes an existing non-TLS Transport and layers a TLS Transport on top of it. This requires the TLS layer to read/write from the underlying Transport using the standard Transport/Protocol interface (i.e. call transport.write() to write bytes, expect protocol.data_received() to be called when bytes are read). The existing (3.4) ssl module cannot do this because the TLS implementation needs to wrap the socket directly; but (presumably) the BIO-based TLS implementation can do this.
Date User Action Args
2015-01-02 04:21:19gvanrossumsetrecipients: + gvanrossum, geertj, pitrou, vstinner, giampaolo.rodola, sbt, yselivanov
2015-01-02 04:21:19gvanrossumsetmessageid: <>
2015-01-02 04:21:19gvanrossumlinkissue22560 messages
2015-01-02 04:21:18gvanrossumcreate