[MacPorts] #68766: openssl3 @3.2.0_0+universal may have broken PRNG on High Sierra and older
MacPorts
noreply at macports.org
Fri Dec 1 07:12:43 UTC 2023
#68766: openssl3 @3.2.0_0+universal may have broken PRNG on High Sierra and older
------------------------+------------------------
Reporter: fhgwright | Owner: neverpanic
Type: defect | Status: closed
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: fixed | Keywords:
Port: openssl3 |
------------------------+------------------------
Comment (by fhgwright):
Replying to [comment:64 fhgwright]:
> Replying to [comment:63 thetrial]:
> > And, in addition: On one of my systems 3.1.4 is uninstalled. Will it
be reloaded or rebuilt?
>
> It will be reinstalled. The epoch bump ensures that the apparent
downgrade in the version number is treated as an upgrade.
However, out of paranoia I decided to test this, and found that upgrading
the individual port failed to do this. See
https://trac.macports.org/ticket/68820.
Replying to [comment:67 thetrial]:
> Yes, thank you very much also from my side.
>
> On one machine I had the problem, that the opoenssl folder was emptied
under libexec, so openssl could not be activated after the first attempt.
I replayed a backup of that folder and tried to force activate, and then
three openssl variants were presented and I could chose 3.1.4+universal (I
guess those were the staged one). After that I just repeated a runthrough
with MP, and it seems, everything is on its path again. I hope.
IIRC, you did some shuffling to try to restore proper operation, which may
have put things in a state that `port upgrade` couldn't fix. In general,
anything that gets the files in the tree inconsistent with the registry
tends to confuse things, and AFAIK there are no automatic recovery tools
for that sort of thing.
--
Ticket URL: <https://trac.macports.org/ticket/68766#comment:68>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list