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, eric.araujo, exarkun, gdamjan, giampaolo.rodola, gregory.p.smith, heikki, jsamuel, lemburg, loewis, mcrute, pitrou
Date 2010-06-29.17:27:40
SpamBayes Score 0.041823093
Marked as misclassified No
Message-id <1277832462.46.0.476091755302.issue8998@psf.upfronthosting.co.za>
In-reply-to
Content
Apart from the question of API, please also include a section on the legal implications this move would have on Python in the PEP.

We currently only include OpenSSL in the Windows installers and (for some reason) don't pay much attention to the implications this has (the fact is not mentioned on the download page and the Windows installer doesn't show the required OpenSSL old-style BSD attribution).

If we are to require OpenSSL or some other crypto lib, possibly even our own (e.g. pycrypto) for all platforms, then we could no longer just ignore the fact that crypto code is subject to strong legislation in many countries of the world.
History
Date User Action Args
2010-06-29 17:27:42lemburgsetrecipients: + lemburg, loewis, gregory.p.smith, exarkun, pitrou, giampaolo.rodola, gdamjan, heikki, eric.araujo, debatem1, daniel.urban, mcrute, jsamuel
2010-06-29 17:27:42lemburgsetmessageid: <1277832462.46.0.476091755302.issue8998@psf.upfronthosting.co.za>
2010-06-29 17:27:40lemburglinkissue8998 messages
2010-06-29 17:27:40lemburgcreate