If you don't want to accept it, then you probably shouldn't post here. That is what this entire site is setup to provide. That is only used for debugging and other utility tasks. But the openssl executable is irrelevant. Now, if I try to run the executable for 1.0.2o, it is going to report version 0.9.8 because that is what is installed at the system level. I link against the 1.0.2o static libraries. I also have openssl 1.0.2o installed in my own directory for my own projects. Lrwxr-xr-x 1 root wheel 15 6 Jun 20:11 /usr/lib/libssl.dylib -> libssl.35.dylibĪnd that is not even all I have. rwxr-xr-x 1 root wheel 1244848 4 Jul 09:02 /usr/lib/libboringssl.dylib You want a more meaningful command? How about this one: The output of that command line is meaningless. I'm in IT and have a ton of client authentication information. In none of the Apple-related product descriptions was their any mention of changes to OpenSSL, so I'm somewhat surprised and unhappy. Within that week, I had updates for iTunes 12.8, Google Earth, Gatekeeper Configuration Data v148 and Security Update 2018-004. I investigated my TM backups and discovered that the new binary had been installed sometime between July 12 and July 18.
#How to update openssl on mac os 10.12 install#
Today, I was preparing to compile and install an update only to discover that my installed OpenSSL had gone from a recent 1.1x version back to 0.9.8zh with a date stamp of June 29. On my Sierra installation with all updates applied, I've been compiling my own OpenSSL due to Apple's apparent abandonment of that part of the OS. If you open Terminal and enter the following command, "ls -l $(which openssl) openssl version", what output do you get?