Alan Coopersmith

@b0rk@social.jvns.ca my attempt at documenting how Unix commands should work for Solaris a decade ago can be seen at https://blogs.oracle.com/solaris/post/collected-advice-on-unix-cli-design-implementation (it was definitely aspirational - things we should do, though many existing commands in Solaris don't do them). It also pointed to an earlier blog at https://monkey.org/~marius/unix-tools-hints.html

@nhbriggs@mastodon.social installing OpenSSL 3 alongside OpenSSL 1 shouldn't have broken anything - that's the default state of Solaris 11.4.42 through 11.4.80 while we worked through converting all the software that used OpenSSL 1 to use 3 instead. But drop-in replacement can't work as they're not compatible (hence the change of major version number) - if you've done something like that, booting from a previous BE is probably your best choice, since the pkg system depends on OpenSSL.

@nhbriggs@mastodon.social the compiled packages from the CBE release are available on http://pkg.oracle.com/solaris/release/ - we're trying to get that updated more frequently going forward (it's been 3 years since the last update there, but even that has both OpenSSL 1.0.2 & 3.0 packages). I don't think we ever offered a mediator to switch between OpenSSL 1.0 & 3.0 because of the incompatibilities.

@nhbriggs@mastodon.social oh, once you had root access, you shouldn't need to recompile, just mount the previous BE and copy the file from there. At this point you probably want to run at least "pkg verify" to see what else was changed, and possibly "pkg fix" to fix it.

@nhbriggs@mastodon.social oh yeah, the OpenSSL 1.0.2 removal changeset requires changes to the core OS packages to stop depending on that version- it wasn’t intended to be installed without them. We’re working on the paperwork now to get an update to the CBE out later this year to cover things like that.