At first glance the SSL connection error may be a different issue (otherwise mangled connection).

sure if you want. main thing about it is the modified dhclient, but should be backwards compatible: github.com/opnsense/src... thanks!

but there wasn't any response there so we are trying to coordinate from a higher level now. Can't say more for the time being. Just hate to see any sub-par rollout, but nothing unfixable. I've said privately I don't mind testing / fixing but we need someone who cares and takes upstream submissions.

Given the release constraints 14.0 is an important milestone and it's good to be officially available now. Keep in mind the pkg repository is "quarterly"default for releases and January will hit hard with the removal of ca_root_nss for certctl use. I've tried to start discussion on a mailing list...

3.0 is LTS and 3.2 isn't ready (not sure if also LTS). The py-cryptography thing is a bit strange as it complains about the default build of OpenSSL 3 in FreeBSD not having legacy.so ... the port is easily fixed but the base system not so much...

For reference see lists.freebsd.org/archives/fre... I've heard this yesterday too that releng was displeased with premature ext. announcements, but having the ability to upgrade into non-ready release sounds strange to me. Fine this way, but this requires different communication strategy?

Fascinating stuff. Get rid of your remaining RSA keys now ;)

hello, so we meet again :D

I don't know. The bug existed there from 2017 till 2023 but somehow they managed to make up a FreeBSD bug that doesn't exist and rant about that. But they've always played hardball there... marc.info?l=openbsd-te...

meh, war gerade erst draussen