2.2K Followers
1,027 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

Officially starting work on #Radicle integration in the #HardenedBSD ports tree.

Once this work is completed, we'll be able to build packages again.

I had originally planned to bring our GitLab instance up in read-only mode this weekend, even though the server it's on is mostly dead. However, I think I'm going to postpone that a little bit longer until this Radicle work is completed.

I restarted the last #HardenedBSD 15-STABLE package build. Tons of ports failed due fetch due to the network issues. Starting it from an incremental state means it should be finished relatively quickly.
We're now mostly alive! IPv6 is having issues, so I've disabled that. But IPv4 access into the #HardenedBSD infrastructure now works.

Even though we cannot currently provide packages and installation media, #HardenedBSD users can fetch the src tree via #Radicle and build the base OS bits.

I'm hoping this weekend to have fully integrated the Radicle distfile download support.

It's now 19:00. I've only clocked in two hours at work. I have a migraine. I still have six hours left to work.

Then I need to work on the #HardenedBSD #Radicle integration with ports.

Right now, folks cannot build their own packages since our #GitLab is down. Our GitLab is down due to the server exhibiting hardware failure after being hammered by AI/LLM web scraping bots too hard over the weeknd.

Now I'm left with a half-working internet connection, no GitLab, and no way to provide our package repos to the public.

Although, our #Tor users should be able to hit our infrastructure again since we provide Tor Onion Service endpoints for our package repos.

That's actually a bright side to this: at least the core part of our "human rights-focused infrastructure" remains functional even while its own infrastructure is crumbling around it (to be clear: the hbsd infrastructure, not Tor, is crumbling.)

My grumpiness level is nearing historic levels today. I'm so very frustrated, tired, angry, and burnt out. Everywhere I go, I just run into problem after problem after problem after problem, and there's no one else to fix them.

Once I shave a few years off my life by tackling these current issues, I think I'm gonna take a break.

I don't have access to my email since my email VM is offline.

The #HardenedBSD dev/build infrastructure will remain offline for the foreseeable future until our ISP situation improves.

Lost enough dexterity over the past couple years that I can't make a single ethernet cable. Giving up after two hours.

I've got things working! I now suspect the problem was my Framework16 laptop, not the server.

Directing #Radicle to point to my other laptop for the initial seed fetch for both src and ports resulted in success!

So we are officially on to the next step of the process: Integrate Radicle support into the #HardenedBSD ports tree.

Now, time for sleep.

I feel like everything is breaking around me and I have no way to recover.