The version of #Nikto in the #FreeBSD ports tree is woefully out-of-date.
Version in ports: 2.1.6
Last official release: 2.6.0
Ouchies. I might try my luck at updating it in the #HardenedBSD ports tree, depending on timeframes at ${DAYJOB}.
The version of #Nikto in the #FreeBSD ports tree is woefully out-of-date.
Version in ports: 2.1.6
Last official release: 2.6.0
Ouchies. I might try my luck at updating it in the #HardenedBSD ports tree, depending on timeframes at ${DAYJOB}.
With this commit, we have resolved the kernel panic plaguing our #HardenedBSD users. This one was a tricky one.

With commit 1aad58b919d3d22f86be01b8e26a203cd020eaae, FreeBSD removed the inclusion of "std.debug" in the GENERIC kernel. This results in a broken kernel on HardenedBSD since we rely on INVARIANTS and WITNESS. This is...
Working on test build number 33 in trying to figure out which commit broke #HardenedBSD 15-STABLE.
Ugh.
I'm giving a remote presentation to the BSD masochistsWusers in New York City in an hour about weird code injection techniques on #FreeBSD
https://www.nycbug.org/media/March2026NYCBUG_Notice_of_Meeting.pdf
Jitsi meeting link: https://jitsi.sdf.org/NYCBUG-2026-03-04_01
YouTube stream: https://www.youtube.com/watch?v=QfGdMrmy0jw
@lw Pre-Forgejo, the #HardenedBSD project tried for a while to use #Gitea. But that fell over sideways with src and ports, especially with scraper bots continuously looking up each and every commit.
At the time, the problem stemmed from the fact that the #golang git package that everyone uses will load the entire repo history just to look up a single commit.
Rinse and repeat for thousands of hits per second, and kaboom!
HardenedBSD currently uses a self-hosted #GitLab Enterprise instance. We're hoping to eventually migrate to #Radicle.
There's a merge conflict in the #HardenedBSD ports tree right now due to #FreeBSD updating ports-mgmt/pkg to 2.6.0.
So, I updated HardenedBSD's fork of pkg and updated the port locally.
Now pkg can't find itself:
$ pkg info pkg
pkg: No package(s) matching pkg
I won't push the merge conflict resolution in ports until I figure out what upstream broke and why.
@bill I live in Colorado. The HardenedBSD server room is in my house. 🙂
The #FreeBSDFoundation is headquartered in Boulder, CO.
The right answer is not to start blocking the tech from the humans who need it most, but rather to fight the legislation, which is what I intend to do when/if it comes to that.
So, no, I'm not gonna stop hacking on #HardenedBSD because of stupid political games.
Everyone is welcomed to use HardenedBSD, regardless of who they are or where they were born or currently reside.