2.2K Followers
1,024 Following
9.9K Posts
HardenedBSD cofounder, Emerald Onion Advisory Board member, all around infosec wonk.
PronounsHe/Him
Email[email protected]
Open to employmentFalse
Tor-ified Signal+1 (303) 901-1600 / shawn_webb_opsec.50

I'm in the job market. Anyone needs senior sys admin, DevOps, #Python and JS/TS all in one who's also medior #Rust, C/C++ and AI developer?

#fedihire #getfedihired

So we have the #HardenedBSD hardened/current/master branch on #Radicle. I pushed the hardened/15-stable/main branch, but on my other system, git branch -r | grep rad shows no other branches, just hardened/current/master.

I'm supposed to add a crefs rule in the identity document, but I'm not sure what that's supposed to look like.

Would it be something like this or something else? I'm a bit confused.

"xyz.radicle.crefs": {
"rules": {
"refs/heads/hardened/*": {
"allow": [ "*" ]
}
}
}
Today, I'm thankful for the last #HardenedBSD server donation, which is our storage server. This is allowing us to backup and transfer VMs from a mostly-dead host to another.
HardenedBSD Build Artifacts

I might just buy the new Framework16 keyboard since I've been experiencing major issues with the existing one.

So, my conversation with Dell to get a quote for a new server: just under $69,000 USD.

I'm gonna guess used servers manufactured in 2020 or sooner are gonna be prohibitively expensive, too.

I don't really see a possibility where the #HardenedBSD project could ever afford any new server, whether brand new or used.

Welcome on Radicle! The repos for src and ports are now seeded on at least six nodes on the network. Most of these are operated by community members. Shout outs go to @defelo, @yorgos, @liw who are supporting with bandwidth and storage in various places in Europe and North America. ✊️

Happy to have your feedback as we continue to work on improving Radicle day by day.

/cc @lattera @aru

It is really heartening and motivating to see the #Radicle community come to aid #HardenedBSD. I'm so grateful folks are helping out, especially at the cost of time, bandwidth, and storage.

I feel full of gratitude this morning.

Looks like today is #FreeBSD Security Advisory day, fixing two vulnerabilities found by Anthropic (CVE-2026-5398 and CVE-2026-6386).

Woke up this morning to new #Radicle seeders for the #HardenedBSD src and ports repos. This is encouraging to see.

There are a number of issues to fix:

  • STALE_CONNECTION_TIMEOUT should either be bumped or made configurable (or both).
  • Filesystem permissions get messed up on #OpenZFS #ZFS but not on UFS or tmpfs.
  • Bump the node.limits.fetchPackReceive maximum by default to higher than 500MiB (exact value to be chosen later.)
  • Improvements to cloning without seeding. Right now, a user will need to run rad seed <RID>, letting both git and radicle to quiet down, then run rad clone <RID>. Otherwise, rad clone <RID> will fail.