OpenBSD 7.4

Earlier submission:<p><a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=37899319">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=37899319</a>

Release image [1] is inspired by works of Louis Wain[2]. Name of the release image references one of his works[3].<p>[1] <a href="https:&#x2F;&#x2F;www.openbsd.org&#x2F;images&#x2F;ImHappyBecauseEveryoneLovesMe.jpg" rel="nofollow noreferrer">https:&#x2F;&#x2F;www.openbsd.org&#x2F;images&#x2F;ImHappyBecauseEveryoneLovesMe...</a><p>[2] <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Louis_Wain" rel="nofollow noreferrer">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Louis_Wain</a><p>[3] <a href="https:&#x2F;&#x2F;arthive.com&#x2F;artists&#x2F;11470~Louis_Wain&#x2F;works&#x2F;466546~Im_happy_for_everyone_loves_me" rel="nofollow noreferrer">https:&#x2F;&#x2F;arthive.com&#x2F;artists&#x2F;11470~Louis_Wain&#x2F;works&#x2F;466546~Im...</a>

Why is this marked [dupe]? This link is the official release page, and the most active discussion for it on HN today.<p>Announcement mail: <a href="https:&#x2F;&#x2F;marc.info&#x2F;?l=openbsd-announce&amp;m=169746103423179&amp;w=2" rel="nofollow noreferrer">https:&#x2F;&#x2F;marc.info&#x2F;?l=openbsd-announce&amp;m=169746103423179&amp;w=2</a>

From a networking perspective, I&#x27;m looking most forward to route-based IPSec tunnels: <a href="https:&#x2F;&#x2F;man.openbsd.org&#x2F;sec.4" rel="nofollow noreferrer">https:&#x2F;&#x2F;man.openbsd.org&#x2F;sec.4</a><p>On the Linux side these are called &quot;vti&quot; devices, and they&#x27;re simpler to use than most other methods, and also the default when interacting with cloud service providers IPSec gateways.

IMHO they really need a two-step release process for changes to pf.conf syntax. In the first step you get a warning when running the service about a deprecated syntax, then drop it. Over the last 20 years I’ve been bitten multiple times by changes to pf.conf which not only breaks your firewall, but invalidates entire published books on pf, countless articles, tutorials, etc.<p>I read some quote from the BDFL once where he said something about breaking changes being good because you’re “in a better place” but I feel the BC breaks are too aggressive to rely on pf directly in anything but small commercial applications. If you want to to tinker and break your home network fine.

Aww, I was most excited about the release song! Is it not happening anymore?

Why was this marked a dupe? Both were posted about the same time, but this one actually has upvotes and discussion...

What people use for hardware now that pcengines&#x27; apus are eol?

I love how OpenBSD continues to support and fix issues on a wide variety of hardware. I personally run it on various machines, from Pentium MMX (1997), AMD K6-3 (1999), to modern machines. 486 support was dropped just a couple releases ago, and was supported longer than VAX.<p>&gt; Fix a bug in the handling of SCSI drives in the bootloader on the luna88k architecture.<p>&gt; Correct undefined behavior when using MS-DOS filesystems, fixes imported from FreeBSD.<p>&gt; On arm64, use the deep idle state available on Apple M1&#x2F;M2 cores in the idle loop and for suspend, resulting in power savings.<p>&gt; Update AMD CPU microcode if a newer patch is available.

OpenBSD has a reputation for being super secure but are there any big organizations that actually use it for security critical applications? A quick search shows outdated or non-related results.

I liked this one<p>* Do not calculate IP, TCP, and UDP checksums on lo(4) interfaces.

Why use an old version of ffmpeg?<p>What is the use of ed25519 x509 TLS certs, which TLS clients support that and which CAs would sign that?