Message 68978 - Python tracker

➜

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	janssen
Recipients	giampaolo.rodola, gregory.p.smith, iElectric, janssen, pitrou, roberte
Date	2008-06-30.01:03:17
SpamBayes Score	0.018750662
Marked as misclassified	No
Message-id	<[email protected]>
In-reply-to

Content
The 2.6/3.0 changes are now up-to-date. We could reconsider this problem. My guess is that we still don't quite know what to do. I think the issue is that we need a way to "unwrap" the SSL-secured TCP stream, after it's been used. So we need to expose the SSL shutdown mechanism (already in the _ssl.c module) in the Python code. Something like socket = self.unwrap() which would return a plain socket.socket instance.

The 2.6/3.0 changes are now up-to-date.  We could reconsider this
problem.  My guess is that we still don't quite know what to do.

I think the issue is that we need a way to "unwrap" the SSL-secured
TCP stream, after it's been used.  So we need to expose the SSL
shutdown mechanism (already in the _ssl.c module) in the Python
code.  Something like

   socket = self.unwrap()

which would return a plain socket.socket instance.

History
Date	User	Action	Args
2008-06-30 01:03:19	janssen	set	spambayes_score: 0.0187507 -> 0.018750662 recipients: + janssen, gregory.p.smith, pitrou, giampaolo.rodola, roberte, iElectric
2008-06-30 01:03:18	janssen	set	spambayes_score: 0.0187507 -> 0.0187507 messageid: <[email protected]>
2008-06-30 01:03:18	janssen	link	issue2054 messages
2008-06-30 01:03:17	janssen	create