[DragonFlyBSD - Bug #3404] update crypto/libressl

[liweitianux]

Issue #3404 has been updated by liweitianux.


sigttou wrote in #note-4:
> Yes, both do that. NetBSD's version is easier to get working on Dragonfly.

I don't know how NetBSD's version differentiate with the LibreSSL's version. I'd prefer the version from the latest LibreSSL, i.e., easier to follow the upstream.

> I can provide a PR to move forward in that way. Porting nc to use OpenSSL, also works, just requires more effort.

> Think the decision is if we want TLS in `nc(1)` or not.

I see that as a nice feature. However, given that FreeBSD/NetBSD's @nc@ and @netcat-openbsd@ (for Linux) all disabled TLS, I don't expect many people will use this non-portable feature.

Anyway, I'd prefer to keep supporting it.

----------------------------------------
Bug #3404: update crypto/libressl
http://bugs.dragonflybsd.org/issues/3404#change-14764

* 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