Rerouted here by Quinn. Asked him a personal question - looks like it's a major one for lots of people.
I noticed something strange SSL happenings inside High Sierra and I am very curious what is it and what are reasons for this..
First of all OpenSSL 0.9.7/8 is still there probably untouched. Which is fine.
Now we have some new libcrypto.40.dylib and .35.dylib files. Which are LibreSSL. Which is surprising. Do we have Xcode/SDK/usr/include/openssl or libressl - nope!
Next we have libboringssl.dylib which is even more surprising. And I can see parts of it in lib system. Also no dev packages.
So.. what’s going on with all those SSL libraries? Why there are so many of them now.
Assume I am a standalone developer that wishes to use OpenSSL on Mac - what will be the recommendations - to self-build it?
And what about Secure Transport - is it still _the primary_ way to use SSL on Mac?
P.S. Shame on removing telnet/ftp. What's next - ping and traceroute?
Best regards,
Platon