Pinned post

I've just updated my GitHub profile! Now, supporters get access to a monthly newsletter with insights on my latest work, project updates, and thoughts on OpenBSD development. Check it out and join the journey.

github.com/sponsors/sizeofvoid

Right, that was a surprise and completely unexpected. I wanted to try out how (8) behaved on . Now it turns out that does not support my Wi-Fi device. That was a short journey. Bye!

"coding is solved" they said
"use AI" they said

me working on OpenBSD writing C: dead software walking
rsadowski.de/posts/2026/dead-s

I have a few tasks in my and backlog. However, I’d be interested to know what you think is missing or what isn’t working properly? Please only reply if you’ve used it or are currently using it. If you’ve used it before, why not?

Just committed support in . The CA privsep engine now handles EC keys too. Big thanks to op@ for migrating the engine + signing code from smtpd.

relayd(8) and httpd(8) TLS settings update.

Both relayd(8) and httpd(8) now have the "secure" list of allowed crypto methods for HTTPS, which include TLSv1.3 and the TLSv1.2 AEAD cipher suites. The previous list was "HIGH:!aNULL" which contain non-perfect-forward-security methods and this change may cause old clients to not be able to connect.

Three days fighting Rust in CMake so KDE Plasma 6.7 can land in OpenBSD ports, then back to httpd & relayd. My g2k26 hackathon writeup: rsadowski.de/posts/2026/g2k26-

By the way, our first two publications on evaluating mitigations are out. Both of these papers evaluate some amd64 anti-ROP mitigations: specifically changing the register selection order and semantically equivalent rewriting of instructions that may produce a potential polymorphic gadget instruction. This tracks a paper by mortimer@ back in 2019 at AsiaBSDCon.

The TL;DR is "OpenBSD can shrink binaries a little and gain a little performance without any security loss simply by reverting these mitigations." The mitigations did not hold up to independent evaluation.

The first paper did an exact 1:1 port of these mitigations to FreeBSD and found that register reallocation eliminates only about 0.3% of unique gadgets, for a 0.5% increase in binary size (mortimer@ claimed 6% reduction and "entirely free"). It is useless at best but more likely actively detrimental, as it produces a false sense of security. It also found the instruction rewriting reduces unique gadgets by about 3.5% with a binary size increase of about 1.8% (mortimer@ claimed 5% reduction with 0.15% binary size increase).

We then did a separate implementation of the instruction rewriting mitigation to GCC in the second paper. Our GCC implementation does the older <xchg; op; xchg> dance, as that's what mortimer@'s paper described. This is way worse; producing about a 3% performance hit for no security benefit at all.

The only part of both mitigations worth saving is for basic arithmetic, OpenBSD LLVM now takes advantage of the fact that basic arithmetic has two forms. For example, the newer instruction rewriting mitigation turns
addq %rax, %rbx (48 01 c3)
into
{load} addq %rax, %rbx (48 03 d8)

The new instruction rewriting mitigation is genuinely free in terms of binary size and execution speed, but doesn't move the security needle, so this one can stay as it is harmless. Other rewritings still have the flaw of increasing binary size and reducing performance for no security benefit.

Anyhow feel free to read the papers:
ieeexplore.ieee.org/abstract/d
researchgate.net/publication/4

If you have the Facebook app on your phone, Mark Zuckerberg would like to monitor your entire life by uploading every photo you take to a secret Facebook database and have AI identify every place you have been, every person you have met, every activity you have participated in, etc.

I do not know how Facebook lures people into turning this on, but I recommend everyone check their settings, and I have made these four pictures which show how you turn it off.

Please reply if yours was on.

I’ve got two new ThinkPads here, but no decent OpenBSD stickers. We need some new OpenBSD stickers! Where can I get something like this printed to a high standard?

It’s my first BSD conference; I’m really looking forward to it.

OpenBSD will ship with the latest Plasma version 6.6.4 :flan_hearts:

Der Vortrag von @sizeofvoid zu den Grundsätzen und (#Security-)Prinzipien von #OpenBSD auf den #CLT2026 war ganz hervorragend. 👍

Selbst ohne BSD-Kenntnisse gut verständlich! Klare Guck-Empfehlung, gerade in Zeiten von AI-Slop und Security-Desastern, die inzwischen teilweise wie Naturkatastrophen behandelt werden.

Show older
BSD Network

bsd.network is a *BSD-adjacent Mastodon Instance. We have a code of conduct.