This month saw a few improvements in HardenedBSD's source tree.

We can now boot to multi-user on the StarFive VisionFive2 riscv64 SBC dev boards. They use a 39-bit address space, so we had to tune down our ASLR deltas for this board as if we were operating on a 32-bit architecture. This is obviously far from optimal, but it's what we have.

Changes to the src tree:

1. Ensure libhbsdcontrol operates only on regular files.
2. Ensure hbsdcontrol does not follow symlinks by default. Provide an option to override.
3. Allow the RTLD ASLR delta to be overridden in the kernel config file.
4. Lower ASLR deltas for StarFive VisionFive2 SBC boards.
5. Drop TCP SYN+FIN packets by default.

In ports:

1. Do not override the default LLVM version in devel/electron32
2. Bring in the -ftrivial-var-auto-init=zero patch from HardenedBSD src for:
   1. devel/llvm17
   2. devel/llvm18
   3. devel/llvm19
3. Bump net-p2p/heartwood-httpd to 0.17.1
4. Disable _FORTIFY_SOURCE for:
   1. x11/swaylock
   2. x11/swaybg
   3. x11-wm/sway
5. Bump hardenedbsd/hbsdmon to 1.0_13
6. Disable PaX PAGEEXEC for www/firefox
7. Set default LLVM version to 19 for 15-CURRENT systems

We performed emergency maintenance on the 14-STABLE build server. We replaced three sticks of RAM. As of this writing, it appears we have to replace more sticks. Once the package build that's running right now finishes, we will do that.

We received a large donation specifically for the purchase of a new Framework laptop. That purchase has been made and we are awaiting shipping. The timing of this couldn't be better as the laptop I used to use for when I'm bed-bound is now too old to run modern HardenedBSD. (The problem being the video card is ancient and there are no supporte drivers for it.) Many of you know I have various random health issues (migraines, back injury, chronic fatigue), so having a more mobile system will help me be active where ever I am.

We will soon be ordering some new hard drives for our NAS server. Once ordered and installed, we will reconfigure how we are storing build artifacts. Right now, each build server has enough storage to store its own build artifacts. However, this means that when we perform maintnance on the build server, the build artifacts are temporarily unavailable. Centralizing artifact storage onto a NAS will enable us to be more efficient when performing maintanance. We plan to make that purchase in January 2025.

I have started a discussion with the FreeBSD Foundation, the HardenedBSD Foundation, the Colorado BSD User's Group, and the Google Summer of Code student Aymeric Wibo, to organize a hackathon in January or February 2025. This hackathon will be geared towards getting the BATMAN-adv mesh networking GSoC work to a state where it can be reviewed for merging into FreeBSD. I'm excited to see where this goes and its human rights impact as we design, build, and deploy surveillance- and censorship-resistant mesh networks.

The HardenedBSD Foundation is happy to announce a donation from the folks over at Protectli. Protectli is an open source firewall appliance company. This is their second donation to the HardenedBSD Foundation to date.

This donation is for a specific project: the development of a censorship- and surveillance-resistant mesh network. Protectli donated four FW4B devices. These devices will help us research and develop a prototype network, with the end goal being wider deployment once the initial proof-of-concept is developed and documented.

We--the HardenedBSD Foundation and the HardenedBSD Project--believe that Protectli offers a solid product line with which to base our reference implementation. We plan to start a concerted effort on the proof-of-concept implementation starting January through February 2025.

We are in talks with a Google Summer of Code contributor for FreeBSD in bringing their hard work to completion; or, at the very least, to a state that is usable for this project. The contributor, Aymeric Wibo, spoke at BSDCan 2024 about his efforts at porting BATMAN-adv to FreeBSD. We hope to bring his work into a special feature branch in HardenedBSD.

Special care must be taken so as not to introduce GPL code. Some bits of the BATMAN project are GPL. The bits that are BSD license compatible can land in the src tree, but GPL bits will land as ports entries.

Once we are satisfied with that work, we will begin work on a special version of HardenedBSD. This version will have all methods for capturing packets (eg, libpcap, tcpdump, BPF, etc.) removed. This would enable network operators to respond to law enforcement requests with a simple answer: "we have no customer data and lack the ability to capture customer data."

We envision networks akin to the NYC MESH project, with two key differences:

1. inter-mesh node connections will be encrypted (IPSEC, Wireguard, or OpenVPN);
2. Supernodes will route all outbound public Internet connections via Tor.

Node and Supernode operators will undergo a vetting process. Supernode operators must also run a public Tor relay to offset the bandwidth cost of users. Routing all traffic through Tor will place a large burden on the Tor network, so we must be kind citizens and try to offset that burden as much as possible.

Protectli plays a crucial role beyond this one donation. We are in talks with Protectli to establish a baseline set of equipment as gold standard. Network operators can supply their own equipment, but we will recommend Protectli as the "known working gold standard reference."

Node operators will be required to run hardened operating systems, with a strong recommendation of HardenedBSD.

We are grateful for Protectli's support of the HardenedBSD project and its goals. We dream of a decentralized digital world wherein safety of its participants is of utmost importance.

If you would like to play a part in this initial research and development, please reach out to the HardenedBSD Foundation at foundation@hardenedbsd.org.

It has been a busy month for me personally, so not too much was accomplished in HardenedBSD.

It got really hot here at home, and the server room's temperatures kept creeping higher than desired. So I spent some time trying to get temperature control more efficient and I made a lot of progress. At the beginning of the month, the server room got up to 76F. After installing foam panels in the window, and doing some more weatherproofing, the room now averages 69F at the hotest, and 60F at the coolest.

I taught our infrastructure monitoring daemon (hbsdmon) how to monitor CPU temperatures. I also taught it how to take action when a monitor transitions from nominal success to failure, and vice-versa. hbsdmon alerts me if the CPU temp hits 80C, and shuts down the server if the CPU temp hits 90C. So now I don't have to worry if I go on vacation, or if the A/C unit dies while I'm asleep. :-)

We received a new server donation. This server will allow us to centralize storage. We'll likely budget for ten 8TB drives (six hot, four spare).

In src:

1. I fixed a kernel panic when a PaX MPROTECT error handling code path was chosen.
2. I coordinated _FORTIFY_SOURCE changes and testing with FreeBSD's Kyle Evans.

In ports:

1. Fabien Amelinck fixed a custom patch we have in ports-mgmt/poudriere-hbsd
2. Shawn Webb fixed x11/station-tweak
3. Shawn Webb enabled PIE and RELRO for textproc/unix2ascii
4. Shawn Webb updated various net-p2p/heartwood* related ports
5. Fabien Amelinck fixed emulators/virtualbox-ose
6. Fabien Amelinck fixed an issue with secadm's manual page path
7. 0x1eef updated the hardenedbsd/sourcezap port
8. Shawn Webb marked math/pspp broken for all supported src branches
9. Shawn Webb updated the hardenedbsd/hbsdmon port

I also published (and deployed locally) a new build of hbsdfw. hbsdfw is a HardenedBSD 14-STABLE based fork of OPNsense that we maintain as a hobby side-project.

As usual, your update process is:

1. Backup your config
2. Reinstall with the new image
3. Restore your config

Default username: root
Default password: hbsdfw

You can find the install media here:
https://hardenedbsd.org/~shawn/hbsdfw/hbsdfw_installer_vga_14.1-20240801...

$ wc -c hbsdfw_installer_vga_14.1-20240801-154128.iso.xz
 1547783764 hbsdfw_installer_vga_14.1-20240801-154128.iso.xz
$ sha256 hbsdfw_installer_vga_14.1-20240801-154128.iso.xz
SHA256 (hbsdfw_installer_vga_14.1-20240801-154128.iso.xz) = 639e87b17fc999acd143c6c731e665f7299a3efe8d551674d0833a475b46cb8e

May 2024 was pretty quiet overall.

In FreeBSD land, The FreeBSD Foundation and Stormshield both sponsored a port of NetBSD's _FORTIFY_SOURCE implementation. Within twenty-four hours, we set _FORTIFY_SOURCE to 2 for the entirety of the base userland and the ports tree. June will see the first 15-CURRENT/amd64 package build with _FORTIFY_SOURCE=2 set by default. I'm sure there will be a lot of fallout to address in ports.

I'm making final preparations to give the HardenedBSD talk at BSDCan. That is the reason I'm writing this status report early. I will post my slides after the conclusion of my presentation.

In ports:

1. 0x1eef updated hardenedbsd/portzap to v0.12.0
2. Shawn disabled fortify source on a few select ports:
   • lang/gcc10
   • lang/gcc11
   • lang/gcc12
   • lang/gcc13
   • multimedia/libv4l
   • devel/libepoll-shim
3. ports-mgmt/poudriere-hbsd was updated to 3.4.1.
4. sysutils/cpu-microcode-intel build was fixed.
5. ports-mgmt/pkg was updated to 1.21.3