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 lemburg
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-21.11:04:53
SpamBayes Score 7.244433e-11
Marked as misclassified No
Message-id <4C989153.2010200@egenix.com>
In-reply-to <1284906329.3205.0.camel@localhost.localdomain>
Content
Antoine Pitrou wrote:
> 
> Antoine Pitrou <pitrou@free.fr> added the comment:
> 
>> 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.

I'll ask Jean-Paul and AB Strakt if they are up to contributing
the pyOpenSSL code to the Python stdlib based on a contributor
agreement. This would enable us to relicense the code undert
the PSF license even if the original code's license is not
changed.

Once that's a done deal, we can then consider moving in the above
direction.
History
Date User Action Args
2010-09-21 11:04:56lemburgsetrecipients: + lemburg, loewis, georg.brandl, gregory.p.smith, exarkun, pitrou, vstinner, giampaolo.rodola, lorph, heikki, eric.araujo, debatem1, dmalcolm, daniel.urban, mcrute, jsamuel
2010-09-21 11:04:54lemburglinkissue8998 messages
2010-09-21 11:04:53lemburgcreate