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 ned.deily
Recipients benjamin.peterson, brian.curtin, christian.heimes, eric.araujo, esc24, georg.brandl, larry, loewis, ned.deily, pitrou, ronaldoussoren
Date 2013-02-08.08:18:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
After spending some time on this, I'm downgrading this from release blocker status.  First, no one has yet identified any immediate need for openssl 1.0.x features to support possible PyPI enhancements, which was my original concern.  Second, since the openssl build system does not support OS X universal builds or SDKs and is not autoconf-based, it does not fit well into the current OS X installer build process.  I have a working first cut of building the libs but there is more to do.  Third, there is the open issue of how to make root certs available.  Ronald, I'm probably missing something obvious here but I don't see which Apple patch you are referring to.  Can you elaborate?

There is also the issue of government export restrictions that seems to always come up with crypto software.  AFAICT, as of a couple of years ago, there is no longer any restriction on shipping openssl binaries with any encryption algorithm from the US to any other country.  There are still a few well-known patent issue which seem easy to avoid.  But I am not a lawyer.
Unless someone objects, I'm going to treat this as a new feature for now and, once ready, we can re-examine backporting.
Date User Action Args
2013-02-08 08:18:57ned.deilysetrecipients: + ned.deily, loewis, georg.brandl, ronaldoussoren, pitrou, larry, christian.heimes, benjamin.peterson, eric.araujo, brian.curtin, esc24
2013-02-08 08:18:57ned.deilysetmessageid: <>
2013-02-08 08:18:57ned.deilylinkissue17128 messages
2013-02-08 08:18:56ned.deilycreate