ODBC can't find correct OpenSSL version after upgrading OpenSSL

Question

Update: if you have this same issue, the source of the problem is being discussed here

After upgrading to Python3.10 with homebrew, my OpenSSL was upgraded to version 3 as well.

Now I can't connect to my SQL Server anymore, since ODBC requires OpenSSL 1.1 or 1.0. So when I run:

isql -v -k "<connection string"

I get the following error:

[08001][Microsoft][ODBC Driver 17 for SQL Server]SSL Provider: [OpenSSL library could not be loaded, make sure OpenSSL 1.0 or 1.1 is installed]
[08001][Microsoft][ODBC Driver 17 for SQL Server]Client unable to establish connection

But when I look in /usr/local/etc/ I see that openssl@1.1 is installed:

How can I solve this problem? Not really familiar with this. So ODBC needs to find the correct OpenSSL version, which is 1.1.

I tried:

ln -s /usr/local/Cellar/openssl@1.1/1.1.1g /usr/local/opt/openssl

Also when I run openssl command, it finds the correct version:

➜  ~ openssl
OpenSSL> version
OpenSSL 1.1.1l  24 Aug 2021
OpenSSL>

Output brew list openssl@1.1

/usr/local/Cellar/openssl@1.1/1.1.1l_1/.bottle/etc/ (7 files)
/usr/local/Cellar/openssl@1.1/1.1.1l_1/bin/c_rehash
/usr/local/Cellar/openssl@1.1/1.1.1l_1/bin/openssl
/usr/local/Cellar/openssl@1.1/1.1.1l_1/include/openssl/ (104 files)
/usr/local/Cellar/openssl@1.1/1.1.1l_1/lib/libcrypto.1.1.dylib
/usr/local/Cellar/openssl@1.1/1.1.1l_1/lib/libssl.1.1.dylib
/usr/local/Cellar/openssl@1.1/1.1.1l_1/lib/engines-1.1/ (2 files)
/usr/local/Cellar/openssl@1.1/1.1.1l_1/lib/pkgconfig/ (3 files)
/usr/local/Cellar/openssl@1.1/1.1.1l_1/lib/ (4 other files)
/usr/local/Cellar/openssl@1.1/1.1.1l_1/share/doc/ (3971 files)
/usr/local/Cellar/openssl@1.1/1.1.1l_1/share/man/ (3971 files)
➜  ~

Output of ls -l /usr/local/opt/openssl/lib/libssl.dylib

lrwxr-xr-x  1 username  admin  14 Sep  7 13:46 /usr/local/opt/openssl/lib/libssl.dylib -> libssl.3.dylib

Also running DYLD_PRINT_LIBRARIES=1 isql -v -k "<connection string" gives me the following. Seems like it is still linked to openssl@3

dyld: loaded:  /usr/local/opt/openssl/lib/libssl.dylib
dyld: loaded: /usr/local/Cellar/openssl@3/3.0.0/lib/libcrypto.3.dylib
[08001][Microsoft][ODBC Driver 17 for SQL Server]SSL Provider: [OpenSSL library could not be loaded, make sure OpenSSL 1.0 or 1.1 is installed]
[08001][Microsoft][ODBC Driver 17 for SQL Server]Client unable to establish connection
[ISQL]ERROR: Could not SQLDriverConnect

1.1.1g is quite old. Please [Edit](https://stackoverflow.com/posts/69463870/edit) your question with the output from `brew list openssl@1.1` and `ls -l /usr/local/opt/openssl/lib/libssl.dylib` — AlwaysLearning, Oct 06 '21 at 11:42
@AlwaysLearning any idea? Have tried everything I could find — Erfan, Oct 06 '21 at 19:47

Erfan · Accepted Answer · 2021-10-08T08:52:09.537

15

After trying many things, I found a (hacky) solution:

I removed the link in /usr/local/opt/:

rm openssl

Created a new link to openssl@1.1

ln -s /usr/local/Cellar/openssl@1.1/1.1.1l_1 /usr/local/opt/openssl

edited Oct 08 '21 at 08:52

answered Oct 07 '21 at 13:09

Erfan

40,971
8
66
78

1

Also being discussed on GitHub [here](https://github.com/mkleehammer/pyodbc/issues/965) – Gord Thompson Oct 07 '21 at 13:20
Which links to [here](https://github.com/microsoft/homebrew-mssql-release/issues/59) – KT12 Oct 14 '21 at 20:40
I got `ln: /usr/local/opt/openssl: No such file or directory`. How to fix this? And ```which openssl /usr/bin/openssl ``` – Fyzzys Oct 17 '21 at 18:43
This worked for me, finally! – Ali Vaseghnia Dec 07 '21 at 02:12

score 0 · Answer 2 · answered Oct 06 '21 at 21:41

Have you tried reinstalling msodbcsql17?

Older versions of msodbcsql17 report a dependency on OpenSSL 1.1:

$ brew deps -n msodbcsql17
m4
libtool
unixodbc
openssl@1.1

Reinstalling msodbcsql17...

$ brew reinstall msodbcsql17
==> Downloading https://ghcr.io/v2/homebrew/core/openssl/3/manifests/3.0.0
######################################################################## 100.0%
==> Downloading https://ghcr.io/v2/homebrew/core/openssl/3/blobs/sha256:ec819e57038f4ae11e3a3e083ec1d37c174e44fce08830bd
==> Downloading from https://pkg-containers.githubusercontent.com/ghcr1/blobs/sha256:ec819e57038f4ae11e3a3e083ec1d37c174
######################################################################## 100.0%
==> Downloading https://download.microsoft.com/download/1/9/A/19AF548A-6DD3-4B48-88DC-724E9ABCEB9A/msodbcsql17-17.8.1.1-
==> Reinstalling microsoft/mssql-release/msodbcsql17 
==> Installing dependencies for microsoft/mssql-release/msodbcsql17: openssl
==> Installing microsoft/mssql-release/msodbcsql17 dependency: openssl
==> Pouring openssl@3--3.0.0.catalina.bottle.tar.gz
==> Regenerating CA certificate bundle from keychain, this may take a while...
  /usr/local/Cellar/openssl@3/3.0.0: 6,415 files, 28.2MB
==> Installing microsoft/mssql-release/msodbcsql17
The license terms for this product can be downloaded from
https://aka.ms/odbc17eula and found in
/usr/local/share/doc/msodbcsql17/LICENSE.txt . By entering 'YES',
you indicate that you accept the license terms.
Do you accept the license terms? (Enter YES or NO)
YES
==> odbcinst -u -d -n "ODBC Driver 17 for SQL Server"
==> odbcinst -i -d -f ./odbcinst.ini
  /usr/local/Cellar/msodbcsql17/17.8.1.1: 10 files, 2MB, built in 9 seconds

After reinstalling or upgrading msodbcsql17, OpenSSL 3 is now reported as a dependency:

$ brew deps -n msodbcsql17
m4
libtool
unixodbc
openssl@3

I did, still gives me the same error `OpenSSL library could not be loaded, make sure OpenSSL 1.0 or 1.1 is installed` — Erfan, Oct 07 '21 at 07:31
I added more information to my question, seems like ODBC can't find openssl1.1 — Erfan, Oct 07 '21 at 07:35
@Erfan That should have fixed it. What does `which openssl` return? — AlwaysLearning, Oct 07 '21 at 08:56

Diana · Answer 3 · 2021-10-21T02:05:14.303

0

I am not sure which link did you remove, since I have all of them in the link below

ls /usr/local/opt: -openssl -openssl@1.1 -openssl@3

Did you remove /usr/local/opt/openssl ? What should we do with /usr/local/opt/openssl@1.1 and /usr/local/opt/openssl@3? Should we keep them?

In addition I don't see 1.1.1l_1 within /usr/local/opt/openssl@1.1.

I tried this: ln -s /usr/local/Cellar/openssl@1.1/1.1.1l_1 /usr/local/opt/openssl This is response I am getting and the same problem is still there: ln: /usr/local/opt/openssl: File exists

Thanks

edited Oct 21 '21 at 02:05

answered Oct 21 '21 at 01:08

Diana

1
1

This is not an answer that helps the original question. If you have a similar problem please, be free to open a new question in order to get help there from the community. – Ali Briceño Oct 21 '21 at 03:00

ODBC can't find correct OpenSSL version after upgrading OpenSSL

3 Answers3

Linked

Related