HardenedBSD @HardenedBSD@bsd.network

Due to a drastic increase in spam/fraudulent accounts in our self-hosted gitlab, we now require an admin approval of new accounts.

After registering, please email netops[AT]hardenedbsd.org to have us activate your account.

Full `dmidecode` output: https://hardenedbsd.org/~shawn/ci-03.dmidecode.txt

Last few `/var/log/messages` entries: https://hardenedbsd.org/~shawn/ci-03-messages.txt

So two sticks are reporting errors.

The #HardenedBSD 15-STABLE build server is experiencing memory issues.

This is the info from `dmidecode` for the sticks installed. They're 16GB ECC DDR3. If anyone can donate, please get in touch.

If you need more info, please also get in touch.

```
==== BEGIN DMIDECODE ====
Handle 0x1100, DMI type 17, 34 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 72 bits
Data Width: 64 bits
Size: 16 GiB
Form Factor: DIMM
Set: 1
Locator: DIMM_A1
Bank Locator: Not Specified
Type: DDR3
Type Detail: Synchronous Registered (Buffered)
Speed: 1600 MT/s
Manufacturer: 002C04B3002C
Serial Number: 0D460465
Asset Tag: 0F143821
Part Number: 36KSF2G72PZ-1G6E1
Rank: 2
Configured Memory Speed: 1333 MT/s
==== END DMIDECODE ====
```

#HardenedBSD 15-STABLE and 16-CURRENT OS updates have been published. These cover the #FreeBSD security advisories announced earlier this week.

#infosec

We have provided two workarounds in this email:

https://groups.google.com/a/hardenedbsd.org/g/users/c/K6TXKOo71OU/m/HEAKJXm_AAAJ

#HardenedBSD

We are testing two candidate patches to address this issue. The first commit caches the new DNSSEC key. The second key switches to the new key.

Initial hand-testing seems to work.

#HardenedBSD

HEADS UP to #HardenedBSD `hbsd-update(8)` users: The #DNSSEC KSK key rollover impacts `hbsd-update`: https://groups.google.com/a/hardenedbsd.org/g/users/c/K6TXKOo71OU

We will keep everyone informed. We also noticed we hit the send button too soon and forgot to update the Subject line. Apologies on that.

The #HardenedBSD August / September 2026 Status Report is out!

This status report also discusses the recent #Radicle security advisory and its impact on HardenedBSD.

https://hardenedbsd.org/article/shawn-webb/2026-09-27/hardenedbsd-august-september-2026-status-report

#FreeBSD #infosec

The #HardenedBSD development infrastructure is undergoing maintenance. Access to our installation media and our package repositories will be intermittently unavailable.

We've now successfully migrated our primary primary nginx server from #bhyve to a regular jail.

Next up is our #Radicle VM, migratine that from a bhyve VM to a jail.

This one will take longer to perform since there's a lot of data to migrate.

#HardenedBSD is announcing a call for donations of enterprise-grade drives: https://groups.google.com/a/hardenedbsd.org/g/users/c/qHref5RxG4E/m/LacY475rCwAJ

Please reach out to @lattera here on the Fediverse or via email (`shawn.webb@hardenedbsd.org`) if you're able to donate.

The #HardenedBSD June / July 2026 Status Report is out!

https://hardenedbsd.org/article/shawn-webb/2026-07-31/hardenedbsd-june-july-2026-status-report

#infosec

HEADS UP: The #HardenedBSD ports tree has been force pushed. This has ramifications for those who use our ports git repository:

https://groups.google.com/a/hardenedbsd.org/g/users/c/o4Fs_RhND5o

#FreeBSD