-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jason R. Mastaler wrote: > Stephen Warren <[EMAIL PROTECTED]> writes: > >>> So tlslite is really the best (Python) TLS/SSL lib out there, eh? >> That I couldn't say - it certainly seemed the easiest to integrate. I >> know there are others though. > > I can't quite understand why this functionality isn't part of the > Python stdlib. Seems strange to me.
I researched this a little, last October I think, when we first discussed native SSL support. It seems that the consensus was that including SSL client support for HTTP, SMTP, etc. was just fine, because a client application simply uses an already existing encryption server. However, by allowing Python to implement an SSL server, this actually creates the opportunity for somebody to create an encrypted channel that otherwise would not have been there. As such, that code would possibly fall foul of the US export regulations on encryption, which wasn't something the Python people wanted to get involved in. This seems a little tenuous to me (the difference between client and server), and I *think* these days it's irrelevant anyway, since I believe one can export SSL grade encryption without a license just fine, but I'm no expert in that area. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF5dMvhk3bo0lNTrURAhjUAJwNfWMj06geoTMizeasRBOZ1OGhZwCcCgKI btfe3JmVwkzf4VXXgYvzk+s= =pLER -----END PGP SIGNATURE----- _________________________________________________ tmda-workers mailing list ([email protected]) http://tmda.net/lists/listinfo/tmda-workers
