I'm pretty sure the LibreSSL that macOS includes is not intended for public linkage.
If you want to ship binaries on macOS that use OpenSSL, the thing to do is to ship your own OpenSSL and update whenever OpenSSL performs a security release. Alex On Tue, Jan 2, 2018 at 7:04 PM, Matt Billenstein <m...@vazor.com> wrote: > On Tue, Jan 02, 2018 at 03:25:17PM -0800, Nathaniel Smith wrote: > > I'm pretty sure that the right solution is to ship your own copy of > > openssl with the build, so that you're totally independent from > Apple's > > ssl shenanigans. Maybe look at how CPython handles this. > > That does seem more common practice -- CPython doesn't do that however, it > links to the old 0.9.8 openssl shipped with OSX since ~10.6. > > So it seems we could try to do the same and say the binary pypy releases > are > compatible that far back, or link to the newer LibreSSL which would support > perhaps Sierra (10.12) and newer. > > m > > -- > Matt Billenstein > m...@vazor.com > http://www.vazor.com/ > _______________________________________________ > pypy-dev mailing list > pypy-dev@python.org > https://mail.python.org/mailman/listinfo/pypy-dev > -- "I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire) "The people's good is the highest law." -- Cicero GPG Key fingerprint: D1B3 ADC0 E023 8CA6
_______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
