summaryrefslogtreecommitdiffstats
path: root/Mac/BuildScript/openssl_sdk_makedepend.patch
Commit message (Collapse)AuthorAgeFilesLines
* Issue #26268: Update OS X 10.5+ installer build to use OpenSSL 1.0.2f.Ned Deily2016-02-151-18/+4
|
* Issue #25798: Update OS X 10.5+ 32-bit-only installer to buildNed Deily2015-12-061-8/+10
| | | | and link with OpenSSL 1.0.2e.
* Issue #24603: Update the OS X 32-bit installer build to use OpenSSL 1.0.2d.Ned Deily2015-07-241-1/+1
|
* Issue #24432: Update OS X 10.5+ installer builds to use OpenSSL 1.0.2c.Ned Deily2015-07-041-1/+1
|
* Issue #23686: Update OS X 10.5 installer build to use OpenSSL 1.0.2a.Ned Deily2015-03-191-8/+8
|
* Issue #23594: Update OS X 10.5 installer build to use OpenSSL 1.0.2.Ned Deily2015-03-061-11/+15
|
* Issue #23212: Update OS X installer build OpenSSL to 1.0.1k.Ned Deily2015-01-091-7/+9
| | | | (currently only used for builds with <= 10.5 deployment targets)
* Issue #17128: Use private version of OpenSSL for 3.x OS X 10.5+ installers.Ned Deily2014-12-131-0/+48
Among other issues, the Apple-supplied 0.9.7 libs for the 10.5 ABI cannot verify newer SHA-256 certs as now used by python.org services. Document in the installer ReadMe some of the certificate management issues that users now need to be more concerned with due to PEP 476's enabling cert verification by default. For now, continue to use the Apple-supplied 0.9.8 libs for the 10.6+ installer since they use Apple private APIs to verify certificates using the system- and user-managed CA keychain stores.