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 daniel.urban, debatem1, dmalcolm, eric.araujo, exarkun, georg.brandl, giampaolo.rodola, gregory.p.smith, heikki, jsamuel, lemburg, loewis, lorph, mcrute, pitrou, vstinner
Date 2010-09-19.14:25:31
SpamBayes Score 4.4655337e-09
Marked as misclassified No
Message-id <1284906329.3205.0.camel@localhost.localdomain>
In-reply-to <4C961B92.9060406@egenix.com>
Content
> pyOpenSSL is stable, in production use and
> has a decent API. The ssl module is good enough for HTTPS client
> use. pyOpenSSL provides a robust server side implementation with
> all the required certificate and context handling needed for this.
> 
> We could tell people to use the ssl module for clients and
> pyOpenSSL for the server side and perhaps integrate the OpenSSL
> package into the ssl namespace.

In this case, this should be decided early, so that I know if I should
continue caring about the ssl module or not. I'm not interested in
maintaining potentially obsolete code.
History
Date User Action Args
2010-09-19 14:25:33pitrousetrecipients: + pitrou, lemburg, loewis, georg.brandl, gregory.p.smith, exarkun, vstinner, giampaolo.rodola, lorph, heikki, eric.araujo, debatem1, dmalcolm, daniel.urban, mcrute, jsamuel
2010-09-19 14:25:31pitroulinkissue8998 messages
2010-09-19 14:25:31pitroucreate