[MacPorts] #71760: OpenSSL-3.4.0 legacy provider improperly built/configured
MacPorts
noreply at macports.org
Sun Jan 5 15:35:17 UTC 2025
#71760: OpenSSL-3.4.0 legacy provider improperly built/configured
-------------------------+--------------------
Reporter: mouse07410 | Owner: (none)
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: openssl3 |
-------------------------+--------------------
Comment (by mouse07410):
Interestingly, if in {{{openssl.cnf}}} I set
{{{
[legacy_prov]
activate = 0
}}}
**and** **explicitly** specify {{{-provider legacy}}} - then Macports
OpenSSL seems to work:
{{{
$ openssl list -providers
Providers:
default
name: OpenSSL Default Provider
version: 3.4.0
status: active
oqs
name: OpenSSL OQS Provider
version: 0.8.1-dev
status: active
pkcs11
name: PKCS#11 Provider
version: 3.4.0
status: active
$ openssl dgst -whirlpool -provider legacy -hex ~/.zshrc
WHIRLPOOL(/Users/ur20980/.zshrc)=
2714940724676c37e299b639c811c678faa93b581c75fc5e85c78f50939835de117a855146248a61e7a7f04cd980f97e20ebc699ee53275b15608a53c41e33ac
$
}}}
I wouldn't care much - but this problem with {{{legacy}}} provider
interfered with installation of Macports python313 (as you can see in the
other ticket https://trac.macports.org/ticket/71730).
--
Ticket URL: <https://trac.macports.org/ticket/71760#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list