HEADS UP: HardenedBSD Infrastructure Maintenance

[Shawn Webb]

Hey all,

This is just a reminder that we will be disconnecting our ISP service
on 23 Apr 2026. Service will be restored on 24 Apr 2026.

Thanks,

--
Shawn Webb
Cofounder / Security Engineer
HardenedBSD

Signal Username: shawn_webb.74
Tor-ified Signal: +1 303-901-1600 / shawn_webb_opsec.50
https://git.hardenedbsd.org/hardenedbsd/pubkeys/-/raw/master/Shawn_Webb/03A4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc

[Shawn Webb]

On Sat, Apr 11, 2026 at 10:33:57PM +0000, Shawn Webb wrote:
> Hey all,
>
> This is just a reminder that we will be disconnecting our ISP service
> on 23 Apr 2026. Service will be restored on 24 Apr 2026.

This email is to serve as a reminder that our dev/build infrastructure
will be offline tomorrow, 23 Apr 2026, and restored the next day.

[Shawn Webb]

On Thu, Apr 23, 2026 at 12:49:33AM +0000, Shawn Webb wrote:
> On Sat, Apr 11, 2026 at 10:33:57PM +0000, Shawn Webb wrote:
> > Hey all,
> >
> > This is just a reminder that we will be disconnecting our ISP service
> > on 23 Apr 2026. Service will be restored on 24 Apr 2026.
>
> This email is to serve as a reminder that our dev/build infrastructure
> will be offline tomorrow, 23 Apr 2026, and restored the next day.

This ISP account change did not go well at all. Our dev/build
infrastructure, including our package repos and installation media,
will remain offline indefinitely.

Our ISP has a tech coming Tuesday the 28th. I won't have reliable
internet at all until our ISP gets their heads out their butts.

[Shawn Webb]

On Fri, Apr 24, 2026 at 10:52:47PM +0000, Shawn Webb wrote:
> On Thu, Apr 23, 2026 at 12:49:33AM +0000, Shawn Webb wrote:
> > On Sat, Apr 11, 2026 at 10:33:57PM +0000, Shawn Webb wrote:
> > > Hey all,
> > >
> > > This is just a reminder that we will be disconnecting our ISP service
> > > on 23 Apr 2026. Service will be restored on 24 Apr 2026.
> >
> > This email is to serve as a reminder that our dev/build infrastructure
> > will be offline tomorrow, 23 Apr 2026, and restored the next day.
>
> This ISP account change did not go well at all. Our dev/build
> infrastructure, including our package repos and installation media,
> will remain offline indefinitely.
>
> Our ISP has a tech coming Tuesday the 28th. I won't have reliable
> internet at all until our ISP gets their heads out their butts.

I'm hoping to land Radicle distfile support in ports over the weekend.
Our package repositories are currently unavailable. Once Radicle
support lands, our users will be able to build packages themselves
until we get our feet back on the ground with regards to our ISP.

Immediately after I land Radicle distfile downloading support, I plan
to update the following ports:

1. ports-mgmt/pkg (the most crucial)
2. ports-mgmt/poudriere-hbsd
3. hardenedbsd/secadm{,-kmod}
4. net-p2p/heartwood* (a few ports)

Once ports-mgmt/pkg is updated, users will be able to build packages
on their own.

Radicle's latest version as of the time of this writing is 1.8.0,
which includes an important security fix. It's a relatively new
release and I suspect most our users do NOT have it installed. You may
need to bootstrap a Radicle node in a Linux environment to initially
fetch the src and ports trees--at least until our package repos are
available again.

I'm tired and need sleep. I hope this message makes sense.

Thanks,

[Shawn Webb]

I've now figured out about 90% of the issues we faced yesterday. We're
still having issues with our tunneled IPv6, but IPv4 works at least.

We now have a workable setup to expose our self-hosted services again.
I have removed the AAAA DNS records to force IPv4 traffic.

Our package repos and installers should be available once again. Next
up is to do that Radicle integration in ports.