<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
	<channel>
		<title>DEF CON Forums - HardenedBSD</title>
		<link>https://forum.defcon.org/</link>
		<description><![CDATA[The HardenedBSD Project is a clean-room reimplementation of the grsecurity patchset for the wider BSD community. (site <a href="https://hardenedbsd.org/">https://hardenedbsd.org/</a>)]]></description>
		<language>en</language>
		<lastBuildDate>Tue, 16 Jun 2026 14:06:00 GMT</lastBuildDate>
		<generator>vBulletin</generator>
		<ttl>60</ttl>
		<image>
			<url>https://forum.defcon.org/images/misc/rss.png</url>
			<title>DEF CON Forums - HardenedBSD</title>
			<link>https://forum.defcon.org/</link>
		</image>
		<item>
			<title>HardenedBSD May 2026 Status Report</title>
			<link>https://forum.defcon.org/node/255799</link>
			<pubDate>Mon, 01 Jun 2026 23:37:09 GMT</pubDate>
			<description><![CDATA[These past two months have been incredibly busy. I didn't publish a status report for April 2026, so this status report will cover that, too. 
 
We have mostly completed the migration from our self-hosted GitLab Enterprise instance to Radicle. There's still further work to be done, but the most...]]></description>
			<content:encoded><![CDATA[These past two months have been incredibly busy. I didn't publish a status report for April 2026, so this status report will cover that, too.<br />
<br />
We have mostly completed the migration from our self-hosted GitLab Enterprise instance to Radicle. There's still further work to be done, but the most crucial bits have made it over. We're also still working on ironing out some kinks in learning &quot;the Radicle way&quot;. I hope soon to write an article chronicling our journey thus far.<br />
<br />
I wrote <a href="https://radicle.network/nodes/rad.hardenedbsd.org/rad:z4Aucnb2nozutuek6o8PC9YfaBeTm#contributing-to-hardenedbsd" target="_blank" rel="nofollow">documentation</a> on how to bootstrap Radicle's local storage directory with src and ports. If you hope to someday submit issues and/or patches, following these bootstrap instructions will certainly ease the initial pain. I plan to include an export of these Radicle storage bootstrap archives with each official build. The current exports are not signed. I'm going to include the hashes in this signed email. I am working on a candidate patch to our build scripts to perform this export. The archives exported by our builder VMs will be signed with our normal ssh key-based signing method.<br />
<br />
Fully fixing the release image generation (chiefly fixing generation of disc1.iso) is my first priority. Radicle bootstrap archive generation is my second priority. Radicle integration in our auto-sync is my third priority. Our commit emails came from GitLab. I need to replicate that functionality but with &quot;the Radicle way.&quot; For now, I'm performing the sync myself when time permits (usually multiple times per day.)<br />
<br />
The past couple months have also seen a number of FreeBSD security advisories, so we've published new builds for 16-CURRENT and 15-STABLE. Installer image generation is still somewhat broken, though I've seen some success with memstick.img. I plan to continue working on this until we're 100% fixed, though it will take time. It takes quite the number of hours to test even the smallest of changes. I get pretty much at most two attempts at testing fixes per day.<br />
<br />
I spent some time studying Reticulum's code. I'm in the process of writing a shim to abstract how its backbone interface implementation uses select and friends. Back when I last looked at it, it required use of epoll. Simultaenously while I was working on that, I did notice the Reticulum project was working on a more portable backbone interface implementation. So I need to restart that research when the time comes.<br />
<br />
I also spent a little bit of time with hbsdfw. I started work on forward-porting our 14-stable hbsdfw-specific patches to 15-STABLE. Then GitLab died, and my priorities switched to the Radicle migration. So I need to restart this research, too, when the time comes. I think I might target -CURRENT rather than 15-STABLE. That way, we don't have to periodically forward-port patches: we just maintain our patches against the naturally-evvolving hardened/current/master.<br />
<br />
We completed the ISP account migration. Some pain is left to resolve. We lost support for our tunneled IPv6 (via Hurricane Electric's Tunnel Broker). I need to schedule a part of my day to capture some packets and get on the phone with some tech support folks on the side of both my ISP and HE. Until then, I've removed the AAAA DNS records for the relevant bits of infrastructure.<br />
<br />
<b>In src:</b><ol class="decimal"><li>FreeBSD merged llvm 21 into base. We needed to fix one compilation error in HardenedBSD's code caught by llvm 21</li>
<li>Replace FreeBSD's README.md with our main wiki-based documentation.</li>
<li>Drop the -HBSD suffix in newvers.sh</li>
<li>Migrate hbsd-update-build to Radicle</li>
<li>Revert the release/ subdirectory to a known good-ish commit. This brought back generation of memstick.img</li>
<li>The hardening.pax.kmod_load_disable sysctl node logic was enhanced</li>
<li>Fix MK_LLVM_LINK_STATIC_LIBRARIES in src.opts.mk</li>
</ol><br />
<b>In ports:</b><ol class="decimal"><li>multimedia/ffmpeg build was fixed</li>
<li>ports-mgmt/pkg was updated to 2.7.5</li>
<li>ports-mgmt/poudriere-hbsd was updated to 3.4.8</li>
<li>A patch was brought in to fix the graphics/hdr_histogram port</li>
<li>hardenedbsd/secadm was updated to account for recent MAC hook changes by FreeBSD</li>
<li>Some incredibly basic support was implemented for downloading distfiles via Radicle HTTP</li>
<li>ports-mgmt/pkg was migrated to Radicle</li>
<li>The default llvm version was bumped to 21 for latest 16-CURRENT users</li>
<li>ports-mgmt/poudriere-hbsd was migrated to Radicle</li>
<li>COMPAT32 was disable for misc/compat{14,15}</li>
<li>PIE was disabled for devel/ccache4</li>
<li>net-p2p/reticulum was migrated to Radicle</li>
<li>hardenedbsd/secadm was migrated to Radicle</li>
</ol><br />
I want to say a heartfelt thank you to the Radicle folks. You've spent a lot of time in helping out. You didn't have to, but you chose to. And for that, I'm incredibly grateful. It's fun to see the Radicle network evolve.<br />
<br />
==== BEGIN ARTIFACT HASHES ====<br />
$ sha256 ports.tar.xz<br />
SHA256 (ports.tar.xz) = b12f303b96b02b16744c1286868726ab4df43a06f6d28de3c2 47d4d1598f743b<br />
$ wc -c ports.tar.xz<br />
1472685664 ports.tar.xz<br />
$ sha256 src.tar.xz<br />
SHA256 (src.tar.xz) = 00301a70910127f4fd9564dca1be948e6b9909e864053a76b9 197565768345cf<br />
$ wc -c src.tar.xz<br />
2069117660 src.tar.xz<br />
==== END ARTIFACT HASHES ====<br />
 ]]></content:encoded>
			<category domain="https://forum.defcon.org/node/240318">HardenedBSD</category>
			<dc:creator>shawn.webb</dc:creator>
			<guid isPermaLink="true">https://forum.defcon.org/node/255799</guid>
		</item>
		<item>
			<title>HardenedBSD February 2026 Status Report</title>
			<link>https://forum.defcon.org/node/255479</link>
			<pubDate>Wed, 04 Mar 2026 21:39:21 GMT</pubDate>
			<description><![CDATA[February saw a few changes in HardenedBSD. The majority of my time was spent chasing down the kernel crash in HardenedBSD 15-STABLE that has been plaguing our users. I worked on narrowing down to a three-day window during which a commit was made that causes the crash. 
 
As I write this, I'm...]]></description>
			<content:encoded><![CDATA[February saw a few changes in HardenedBSD. The majority of my time was spent chasing down the kernel crash in HardenedBSD 15-STABLE that has been plaguing our users. I worked on narrowing down to a three-day window during which a commit was made that causes the crash.<br />
<br />
As I write this, I'm narrowing that down further to the specific commit. I'm hoping to have this resolved this month. If I find and fix the problem this week, I will create new builds for folks to use. Otherwise, the next scheduled regular quarterly build is for 01 Apr 2026.<br />
<br />
I appreciate everyone's patience on this. This has been a tricky bug (at times, it fit the description of a &quot;heisenbug&quot;). My spare time is limited (I have a rather large amount of tasks/obligations in everyday ${LIFE} right now), so it has naturally taken a long while to get to this point.<br />
<br />
While inbetween clients at my dayjob, I have been granted the opportunity to research meshtastic and other mesh networking projects. I'm getting a lot closer in my censorship- and surveillance-resistant mesh network proof-of-concept. I'm now at the point where I need to port Linux-specific code to HardenedBSD. I'm hoping to get normal tcp/ip packets flowing through Reticulum nodes on the inside of six months. This project, <a href="https://hardenedbsd.org/article/shawn-webb/2024-09-23/hardenedbsd-and-protectli-collaborates-censorship-and-surveillance" target="_blank" rel="nofollow">announced</a> in partnership with Protectli one-and-a-half years ago[1], is starting to move along at a nice pace. I will have more to share on that by the next status report.<br />
<br />
On Saturday, 28 Feb 2026, I had given my local Hackers N' Hops chapter a little show &amp; tell of Meshtastic, Reticulum, and HardenedBSD. I met with a bunch of really cool hacckers there, and demoed two Reticulum RNodes backed by Reticulum instances on two HardenedBSD laptops. I demoed an exec-over-meshtastic Python script I wrote the day prior. The script is available on Radicle as rad:z44pvAJS7SiQf2CGtpn8hY44GDMyu.<br />
<br />
Speaking of Radicle, I plan to migrate some of my personal repos away from our self-hosted GitLab and onto the Radicle network. With time, I'm hoping to migrate us completely towards Radicle. Now would be a good time for those who want to contribute to HardenedBSD to start playing around and experimenting with Radicle.<br />
<br />
<b>In src:</b><ol class="decimal"><li>Contributor &quot;gmg&quot; hardened the kernel crashdump interface.</li>
<li>Opt zlib kernel module into -ftrivial-var-auto-init=zero.</li>
<li>bsdinstall(8): Align us more closely with FreeBSD.</li>
</ol><b>In ports:</b><ol class="decimal"><li>net-p2p/reticulum was updated to 1.1.3_2</li>
<li>Disable PaX PAGEEXEC and PaX NOEXEC for science/zotero</li>
<li>Bring in candidate patch to fix dns/unbound</li>
<li>Hook hardenedbsd/ctrl into the build</li>
<li>0x1eef added a new port: hardenedbsd/ctrl</li>
<li>Bump ports-mgmt/pkg to 3.5.1_1</li>
<li>0x1eef updated a port: portzap v2.1.1</li>
<li>0x1eef updated a port: sourcezap v2.1.1</li>
</ol><br />
Once I have figured out what's going on with the 15-STABLE panic and have a proper fix in place, I plan to quickly switch gears towards hbsdfw. I haven't produced a working hbsdfw build in a long time, and it's far past due. After that, I plan to switch right back to the Reticulum research and development.<br />
<br />
I'll make sure to keep the community informed of the 15-STABLE findings and fixes.<br />
 ]]></content:encoded>
			<category domain="https://forum.defcon.org/node/240318">HardenedBSD</category>
			<dc:creator>shawn.webb</dc:creator>
			<guid isPermaLink="true">https://forum.defcon.org/node/255479</guid>
		</item>
	</channel>
</rss>
