Author gvanrossum
Recipients Elizacat, gc, gvanrossum, haypo, yselivanov
Date 2015-04-27.17:43:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1430156600.34.0.866125144493.issue23749@psf.upfronthosting.co.za>
In-reply-to
Content
We didn't do this originally because the 3.4 SSL module didn't have this functionality (or maybe it was 3.3 that didn't have this) but now that we do have it I'd be very happy if you could implement this!

I'm not sure what the right interface is, probably coroutine methods on StreamReader and StreamWriter that take an SSLContext object (and from then on the reader/writer is using SSL), but there also would have to be a lower-level way to do the same thing to a Transport. This would probably have to return a new Transport that uses the original, wrapped transport for reading/writing.

You probably should write a small test app that proves this works for real too. Perhaps start with a synchronous test app that uses the existing wrap_socket() and then work on the async interface until you can reproduce the same thing there.

Let us know if you need more information.
History
Date User Action Args
2015-04-27 17:43:20gvanrossumsetrecipients: + gvanrossum, haypo, yselivanov, Elizacat, gc
2015-04-27 17:43:20gvanrossumsetmessageid: <1430156600.34.0.866125144493.issue23749@psf.upfronthosting.co.za>
2015-04-27 17:43:20gvanrossumlinkissue23749 messages
2015-04-27 17:43:20gvanrossumcreate