Sponsors
Sponsor Products
Looking for an immediate solution to upgrading OpenSSL on OS X Sierra
posted by Dan Walekr  on May 14, 2019, 1:35 p.m. (3 months, 4 days ago)
2 Responses     0 Plus One's     0 Comments  
Hey everyone,   Anyone solve the [Mac OS X Sierra] issue of having older [Python 2.7.13 /  OpenSSL 0.9.8zh 14 Jan 2016 ] installed?  Needing a solution ASAP.  PyEnv hasn't been of any help as I've found this to only be useful in a shell environment.  I've been down all the rabbit holes and all of them lead to setting up your Shell environment and NOT setting up an upgraded version of Python and OpenSSL on a system wide level.   I've also gone as far as installing Python 2.7.16 which installs in [/Library/Frameworks/Python.framework/Versions/2.7/bin/python] but OpenSSL is still pointing to OpenSSL 0.9.8zh 14 Jan 2016 from a system level.


Clarks-iMac:~ testuser$ which python
/usr/local/bin/python
Clarks-iMac:~ testuser$ python -V
Python 2.7.16

Clarks-iMac:~ testuser$ which openssl
/usr/bin/openssl
Clarks-iMac:~ testuser$ openssl version
OpenSSL 0.9.8zh 14 Jan 2016

I've tried pretty much everything that I've been able to gather from the web but all information is relative to setting this up to work in a Terminal/Shell environment.     Thanks in advance for any help you can offer!!!   Best,   Dan Walker walkerdan1@gmail.com

Thread Tags:
  sierra python, openssl, os x 

Response from Seth Noble @ June 10, 2019, 9:55 a.m.

Different applications can have different ways of finding resources like Python and OpenSSL, so it really depends on the particular applications you are interested in and what their dependencies are.  Some may have their own internal distributions, some may not be compatible with new versions, and some may depend on macOS specific extensions.  

The challenge is figuring how how a particular application is finding its resources and putting the new versions where it can see them.  Just remember that while you can lead an application to libraries, but you can't make it link.

Here are some approaches:

* Look in the application package to see if it has private copies of the libraries.  If it does, make a backup of the application and try replacing the libraries/frameworks directly.  This will break the application signature.

* If it is not using private libraries, use "otool -L" on the application executable to find its linking dependencies.  For example, "otool -L /Applications/Pages.app/Contents/MacOS/Pages".

* If it is linking to /System versions, try modifying its library search path by uisng LSEnvironment in its Info.plist to change LD_LIBRARY_PATH, LC_LOAD_DYLIB, or LC_RPATH.  This will also break the application signature.  The following article may help:

https://medium.com/@donblas/fun-with-rpath-otool-and-install-name-tool-e3e41ae86172

* If all else fails, and you REALLY want to replace those libraries, you could disable System Integrity Protection and install into /System/Library.  But that could create system wide stability problems, reduces security of the overall system, and may create problems when you try to upgrade the system.

 


0 Plus One's     0 Comments  
   

Response from Kirolous Frouk @ June 4, 2019, 9:23 p.m.

Are you able to try brew ? and thier openssl install https://formulae.brew.sh/formula/openssl


0 Plus One's     0 Comments