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 pitrou
Recipients Andrew.Grover, baikie, brian, exarkun, giampaolo.rodola, jackdied, ncoghlan, neologix, pitrou, python-dev, rosslagerwall, synapse, therve, vstinner, wiml
Date 2011-08-23.11:31:38
SpamBayes Score 0.0023177161
Marked as misclassified No
Message-id <1314098959.3485.1.camel@localhost.localdomain>
In-reply-to <>
> However, in doing this, I noticed that these methods will, at best,
> work during the time between connection and the socket going secure
> and were not added to the list of methods that the SSL is documented
> as exposing. Perhaps we should just ditch them entirely?

Well, apparently the SSLSocket object is meant to be usable in clear
text mode. I'm not sure why it's like that, but your patch looks ok to
me (except that it has a debug print() call).
Date User Action Args
2011-08-23 11:31:39pitrousetrecipients: + pitrou, exarkun, ncoghlan, therve, vstinner, jackdied, baikie, giampaolo.rodola, synapse, Andrew.Grover, wiml, neologix, rosslagerwall, python-dev, brian
2011-08-23 11:31:38pitroulinkissue6560 messages
2011-08-23 11:31:38pitroucreate