On 1/11/2017 8:09 AM, Ronald Oussoren wrote:
On 10 Jan 2017, at 21:47, Ned Deily
wrote: Annoyingly with OpenSSL on OSX you have to options: either use an up-to-date release or have OpenSSL use the system CA trust store, but not both. Sigh…
It would be nice if someone would do the work to figure out whether it is feasible to use Apple's own Crypto and TLS API's as apparently libcurl does.
This should be possible, although I don’t know if the relevant Apple API’s are safe to use after forking (which has bitten us in the past for other Apple APIs, such as the _scproxy extension that detects proxies on OSX).
Sadly enough I don’t really have time to look into this.
While I'm sure this isn't a newbie "easy" issue, maybe open an issue for it on the bug tracker and someone will find it and work on it? I'd open it myself, but I don't know enough about it to phrase the problem correctly! Eric.