#HardenedBSD bug report: https://radicle.network/nodes/rad.hardenedbsd.org/src/issues/746623c1093a6813256cba7162bbf54f3cfb4170

Update the hardening(4) manual page

If writing mandoc is your thing, and you would like to contribute to HardenedBSD, please submit us a patch over #Radicle.

If you're unfamiliar with Radicle, I can help step you through the initial process of getting started (on a HardenedBSD system, of course.) Getting familiarized with their User Guide is a good first step: https://radicle.dev/guides/user

Hrmm, I guess Reddit shadowbanned me for being too polite.

So, I think I might make this more formal via email and announcement, but this has been taking up a large chunk of mental space. I desperately need help in developing HardenedBSD. While I'm so grateful for the many kind and encouraging words, there's still so many hours in a day.

I'm also very grateful we have one person who recently has stepped up, helping move the Pledge port ahead (and closer to full API compat.)

Please consider this post as unofficial. This is just "my thoughts as I've experienced them the past few days." If something comes from publicly posting my thoughts, all the better.

I'm wondering if anyone knows any folks interested in the kinds things we do at HardenedBSD. specifically looking for folks to mentor to do either osdev on hbsd itself, or in developing the censorship- and surveillance-resistent mesh network proof-of-concept.

i could budget a small amount for acquiring HaLow mesh gear. i don't have the budget for a laptop or other equipment. the only requirement is that all this R&D work be done on HardenedBSD.

When it comes to hardware acquisition, it's hard to know who to trust. I would like to make sure donated funds used properly and don't want to be scammed.

On the osdev side, I would like an implementation of random fd assignment. open(2) and friends usually just use the first available number, increasing until maxfd limit is hit.

i would like to change it to be less predictable, to a random search mode rather than incremental search.

This would help mitigate file descriptor reuse bugs.

Of course, we would collaborate via #Radicle for any development work.

One last thing: I should be explicit in that all this is unpaid volunteer work. I have never received payment for my work and don't intend to.

I understand that a large portion of volunteer work fizzles out or doesn't work out. That's fine. I would just expect return to the HardenedBSD Foundation of any procured hardware.

#HardenedBSD #infosec #osdev

Working on test build number 33 in trying to figure out which commit broke #HardenedBSD 15-STABLE.

Ugh.

Anyone know of anyone making and selling fully complete outdoor solar #Meshtastic nodes? I'm at the point in my experimentation where I could use two permanent devices.

Almost 11pm. been awake since 3am. can't sleep. ugh.

Current status: Building packages on my #HardenedBSD OPSEC laptop that sits on my fully Tor-ified network.

The goal here is to build #Reticulum and #NomadNet so I can test them behind #Tor.

#TorProject #infosec

So I'm looking to supplement my current income with around 10hr/week 1099 engagements. I would be happy doing sysadmin or software development work.

My resume: https://hardenedbsd.org/~shawn/2026%20Shawn%20Webb%20Resume.pdf

#FediHire

I was hoping to deploy the #HardenedBSD 15-STABLE build server today, but my body has other plans. Still dealing with vertigo-induced nausea. I'm glad I was able to update our main web server today, but I think that might be all I do today.

Time for me to go back to bed.

Please never ever do this: https://ergaster.org/posts/2025/07/28-direnv-bitwarden-integration/

#infosec

The reason I usually say "the missus" is because I don't like the possessiveness of "my wife". she's her own person, I don't own her.

you'll still see me say "my wife" sometimes because grammar is tricky. but mostly, I stay with "the missus".

This scam technique is new-to-me. Interesting.