HardenedBSD Planned Maintenance

[Shawn Webb]

Hey all,

I plan to apply updates across the entire development/build
infrastructure on Saturday, 31 Jan 2026. I plan to make the package
repo hosting switch on that date.

Affected services include (but may not be limited to):

1. https://vaultwarden.hardenedbsd.org/
2. https://git.hardenedbsd.org/
3. https://installers.hardenedbsd.org/
4. The package repos

I will keep everyone informed as to when I start and when I complete.
I do suspect my WAN IP to change, so when I give the go-ahead, you may
need to clear DNS resolver cache.

Thank you for your patience and understanding.

Please let me know if you have any questions, comments, or concerns.

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 Mon, Dec 29, 2025 at 09:27:30PM +0000, Shawn Webb wrote:
> Hey all,
>
> I plan to apply updates across the entire development/build
> infrastructure on Saturday, 31 Jan 2026. I plan to make the package
> repo hosting switch on that date.
>
> Affected services include (but may not be limited to):
>
> 1. https://vaultwarden.hardenedbsd.org/
> 2. https://git.hardenedbsd.org/
> 3. https://installers.hardenedbsd.org/
> 4. The package repos
>
> I will keep everyone informed as to when I start and when I complete.
> I do suspect my WAN IP to change, so when I give the go-ahead, you may
> need to clear DNS resolver cache.
>
> Thank you for your patience and understanding.
>
> Please let me know if you have any questions, comments, or concerns.

Hey all,

This is a reminder that we plan to perform maintenance across the
entire development/build infrastructure this coming Saturday, 31 Jan
2026.

I'm getting ready to do more than what was originally planned. I plan
to restructure the network to allow for tagged VLANs. We aquired three
GL.iNet Comet Pro IP KVMs for our three main servers (git, 15-stable
builder, 16-current builder). The iDRAC in these refurbished Dell
servers is old enough to be considered a major security problem,
including not even supporting TLSv1.2.

I'm also hoping to revisit the 15-STABLE deployment on our storage
server. After producing the last builds to address the recent security
advisories, I attempted updating the storage server from 14-stable to
15-stable, resulting in a boot loop immediately when the bootloader
attempts to hand control over to the kernel.

I've not debugged issues at such an early boot stage. I've got a few
gaps of knowledge to fill to be able to tackle that issue. But that's
a core part of the Comet Pro purchase: to be able to better see what's
going on (and take action remotely).

So, Saturday's gonna be a long day. I'll keep everyone informed as to
when I start the maintenance and when I've completed it.