[MacPorts] #63857: After upgrading packages to latest, including OpenSSL 3.0, Python can no longer use ripemd160

MacPorts noreply at macports.org
Mon Nov 8 06:53:03 UTC 2021


#63857: After upgrading packages to latest, including OpenSSL 3.0, Python can no
longer use ripemd160
-----------------------+--------------------
  Reporter:  cculianu  |      Owner:  (none)
      Type:  defect    |     Status:  new
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:
Resolution:            |   Keywords:
      Port:            |
-----------------------+--------------------
Description changed by cculianu:

Old description:

> Python 3.8, 3.9, and 3.6 can't now use the hashlib hasher "ripemd160",
> even though that hasher is listed as "available".
>
> I suspect it has to do with the new OpenSSL3.0.  Can we please revert
> back to 1.1? It seems 3 has caused a bunch of problems already (see my
> other ticket related to tor not building).

New description:

 Python 3.6, 3.7, 3.8, and 3.9 can't now use the hashlib hasher
 "ripemd160", even though that hasher is listed as "available".

 As part of the upgrade both openssl3 and Python3.x (all 4) were rebuilt.
 I'm on Big Sur.

 I suspect this new problem has to do with the new OpenSSL3.0.  Can we
 please revert back to 1.1? It seems 3 has caused a bunch of problems
 already (see my other ticket related to tor not building).

 I had to manually modify my /opt/local/var/ macports stuff to force
 macports to use openssl1.1, and then I told it to reinstall Python3.9, and
 now that works.

 The problem is most definitely related to openssl3.

--

-- 
Ticket URL: <https://trac.macports.org/ticket/63857#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list