[DragonFlyBSD - Bug #3404] update crypto/libressl
liweitianux
bugtracker-admin at leaf.dragonflybsd.org
Fri Oct 2 03:17:00 PDT 2026
Issue #3404 has been updated by liweitianux.
I'm not a heavy user of @nc(1)@, so I don't really know whether it's worth the efforts to port LibreSSL's @nc@ to also support OpenSSL. (I think that shouldn't be hard.) On the other hand, there is @openssl s_client/s_server@ for TLS.
By the way, it seems both NetBSD's and FreeBSD's @nc(1)@ were ported from OpenBSD but removed/disabled the TLS support.
----------------------------------------
Bug #3404: update crypto/libressl
http://bugs.dragonflybsd.org/issues/3404#change-14739
* Author: pmjdebruijn
* Status: New
* Priority: Normal
* Assignee: liweitianux
* Target version: 6.6
* Start date: 2026-02-24
----------------------------------------
Currently LibreSSL in base DragonFly is stuck at 3.6.1, which is quite outdated, and while it's current use may be not that critical, having such a dated library installed is still a risk of an application is unintentionally linked against it.
One possibility would be to just upgrade LibreSSL to a newer version...
However, maybe it's worth considering to move to OpenSSL 3.5 LTS, which may be easier to keep up to date over the foreseeable future.
Having this backported to 6.4 would be a nice to have...
--
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account
More information about the Bugs
mailing list