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-19.10:52:30
SpamBayes Score 5.7250316e-11
Marked as misclassified No
Message-id <4C95EB6C.5050104@egenix.com>
In-reply-to <1284850462.96.0.244805154384.issue8998@psf.upfronthosting.co.za>
Content
Just another data point for the discussion:

The PSF is currently funding the effort to port pyOpenSSL to
Python 3.x and the port is nearly finished.

It may be worthwhile investigating adding the EVP interface
from evpy (with the ctypes bindings converted to real C wrappers)
to pyOpenSSL and then adding the pyOpenSSL package to the stdlib.

Note that going for other crypto libs than OpenSSL is currently
not an option, since those are not widely available on the OSes and
we cannot easily add crypto code itself to Python's stdlib due to the
issues with crypto import/export/use restrictions which would
limit the use of Python in various countries.
History
Date User Action Args
2010-09-19 10:52:32lemburgsetrecipients: + lemburg, loewis, georg.brandl, gregory.p.smith, exarkun, pitrou, vstinner, giampaolo.rodola, lorph, heikki, eric.araujo, debatem1, dmalcolm, daniel.urban, mcrute, jsamuel
2010-09-19 10:52:31lemburglinkissue8998 messages
2010-09-19 10:52:30lemburgcreate