#libressl
#OpenBSD 7.7 has been released (#BSD / #NetBSD / #386BSD / #Unix / #LibreSSL / #OpenSSH / #OpenBGPD / #OpenSMTPD / #OpenNTPD / #OpenIKED / #rpkiClient / #mandoc) https://openbsd.org/
Released: #swad v0.1 
Looking for a simple way to add #authentication to your #nginx reverse proxy? Then swad *could* be for you!
swad is the "Simple Web Authentication Daemon", written in pure #C (+ #POSIX) with almost no external dependencies. #TLS support requires #OpenSSL (or #LibreSSL). It's designed to work with nginx' "auth_request" module and offers authentication using a #cookie and a login form.
Well, this is a first release and you can tell by the version number it isn't "complete" yet. Most notably, only one single credentials checker is implemented: #PAM. But as pam already allows pretty flexible configuration, I already consider this pretty useful 
If you want to know more, read here:
https://github.com/Zirias/swad
I can't count how many times I've put import requests behind a warnings filter after urllib3's developers decided they can dictate what libraries the end user has.
Recent and not so recent changes in OpenBSD that make life better (and may turn up elsewhere too) https://nxdomain.no/~peter/blogposts/recent-and-not-so-recent_changes_in_openbsd_that_make_life_better.html from 2021 but has aged surprisingly well #openbsd #freesoftware #libresoftware #libressl #ssh #pf #laptops
https://x.com/openbsd/status/1889330772399501381
LibreSSL is not affected by the OpenSSL vulnerabilities announced today.
@rmbolger @drwho @cacert Either way, @letsencrypt should not push such #bloatware becaise there's no valid reason for it.to come.with it's own version of cat, dd and other tools bundled with it...
Goal: Get some #letsencrypt certificate obtained with #uacme deployed on some #Windows box
Step 1: Ok, this probably works best with #Powershell (which I don't really like ...)
Step 2: There's no #FreeBSD port ... but hey, there's now a FreeBSD port of #dotnet, let's try to "just" build Powershell using that.
Step 3: Hell why does it fail to build. Oh, System.Security.Cryptography.Native doesn't play well with #LibreSSL
Patch and retry, I guess I'll take some sleep now first. Bah!
(there's some irony in running into OpenSSL/LibreSSL issues when trying to deploy TLS certificates ...)