19:52:31 <tsoome> am I the only one with: root@beastie:/code/illumos-gate# ssh
19:52:31 <tsoome> OpenSSL version mismatch. Built against 3050003f, you have 30500040
20:16:41 <andyf> Joy. OpenSSL reverted their version numbering change in 3.5.4 but it means ssh will need to be rebuilt
20:18:00 <wacki> @tsoome: This happens if your openssl-3 build is newer than the openssh build. After each openssl-3 update we have to rebuild openssh. You may have updated your system in a moment where the openssh rebuild wasn't yet published.
20:19:18 <andyf> That was only necessary for the move from 3.5.2->3.5.3, and then again for 3.5.3->3.5.4 because of a mistake by the openssl team (at least that is how I'm going to characterise it). Future upgrades within the 3.5.x train shouldn't need an openssh rebuild.
20:25:14 <wacki> I only followed the discussion after the first problematic update. The openssl people wrote that the openssh developers were too strictly checking the version number IIRC.
20:26:41 <andyf> Yes there were come comments like that, but in the end they realised that that had always documented that the last 8 bits were zero so they reverted the change. It was always a bit of a strange thing to do in the middle of a release train.
20:27:29 <andyf> https://github.com/openssl/openssl/commit/ce2a6deb81e9c4a92fc0985983a1b4e42b543330
20:27:30 <fenix> → GitHub commit ce2a6de: Fix OPENSSL_VERSION_NUMBER to always have zero status bits (committed)
20:27:54 <andyf> 4 bits, not 8..
20:42:36 <tsoome_> hm, yep, had a bit older ssh:)