[MacPorts] #71760: OpenSSL-3.4.0 legacy provider improperly built/configured
MacPorts
noreply at macports.org
Sun Jan 5 22:10:29 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):
@Ken, I assume you installed "stock" OpenSSL, i.e. - did ''not'' modify
{{{openssl.cnf}}}? Your binaries were built on your machine locally
(probably), or on a buildbot?
In any case, I'd be interested in seeing the part of your
{{{openssl.cnf}}} that defines providers.
"M1 vs. M2" is such a long shot that I refuse to seriously discuss it yet.
A likelier possibility is a bug in OpenSSL related to the number of
providers enabled, and the sequence in which they are loaded.
1. Would you mind showing the output of your {{{openssl list -providers
-verbose}}}?
2. Is it feasible for you to install other providers, minimum - OQS and
PKCS11 (see the list of providers I posted a few messages earlier), and
try again?
3. Probably not for you - but OpenSSL-3.4 (upstream) was supposed to get a
fix backported, so it would be great if somebody could update the OpenSSL
port to pull that fix in.
--
Ticket URL: <https://trac.macports.org/ticket/71760#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list