Notices by Nick Briggs (nhbriggs@mastodon.social)

@alanc Thanks. I think the previous BE will be the only option. I didn't intend to do a drop-in replacement. I think instead of setting mediators (apparently incorrectly, such that it immediately switched to 3) I should have removed the links that the Userland openssl3 was trying to make for /usr/lib/libcrypto.so that conflicted with the openssl-1.x. Yeah, I've borked the pkg system. Wish Oracle would release Userland compiled packages to those of us with personal machines.

@alanc Might I ask a favor? Is there a way to recover from having installed openssl-3 on a personal Solaris 11.4 system which seems to have broken everything relying on openssl 1.0.x -- including "sudo" and the "pkg" system? I haven't been able to find any discussion in the regular places.

@alanc Success. Since I still had an unprivileged session active (and nobody else did), got someone with role=root to share their password. Normally I can sudo for admin, but couldn't when libcrypto.so.1.0.0 was not locatable. I recompiled a 1.0.2t openssl, and with su thatuser and su root put libcrypto.so.1.0.0 into the expected place. Everything is back to normal. Now to figure how I screwed it up.

@alanc Good idea. There were a lot of things I couldn't do even with root, because some system python modules still depend on libcrypto 1.0.0 (ref: no recent updates to CBE) -- I think these are things I can't update because they're not part of userland. I tracked down what burned me - the openssl-3 package got updated, 16e0fabcd61e, "PSARC/2024/024 EOF OpenSSL 1.0.2, 35041813 EOF of openssl-1.0.2 library: Removal" and it replaced openssl@1.0.2 with openssl@3.0.16 removing libcrypto.1.0.0