OpenBSD 8.0 arrives with security record still intact

Hardware & Components

OpenBSD 8.0 Ships With 512 GB Address Space and Intel Arc Support

OpenBSD 8.0, the 61st release since 1996, adds Intel Arc support and a 512 GB kernel address space. De Raadt cites two remote holes in 30 years.

By
Tom Whitfield
Filed
Channel
Hardware & Components
Read
3 min read

OpenBSD 8.0 arrives as the project's 61st release, and its founder claims a security record few operating system vendors can match: more than thirty years with only two remote holes in the default install. In a post to the project's announcements mailing list, founder Theo de Raadt said the team remains "proud of OpenBSD's record of more than thirty years with only two remote holes in the default install." The release continues the project's semiannual cadence, which it has held without interruption since 1996.

The new version carries two changes that matter most for hardware compatibility. First, the system now supports Intel Arc A-Series graphics cards, built on the DG2 (Alchemist) silicon family. Second, the AMD64 kernel's virtual address space expands from 4 GB to 512 GB. That jump lets the system map more than 4 GB of video RAM directly, which had become a practical limit for modern graphics cards.

For a project that began more than thirty years ago as a fork of NetBSD, the release shows where OpenBSD is investing its engineering effort now.

What else does 8.0 add?

The release newsletter lists a broad set of changes beyond graphics:

  • Hibernation support for ARM64 systems.
  • A new RPKI-to-router daemon, rtrd(8), for route validation infrastructure.
  • RISC-V kernel support for the 'V' vector extension and for the Advanced Interrupt Architecture.
  • Wireless driver work, including 802.11n and 40 MHz channels in the qwx(4) driver.
  • Support for up to 64 virtual CPUs per guest virtual machine.
  • Improvements to the vmm/vmd virtualization stack.
  • Security and internal updates in LibreSSL 4.4.0 and OpenSSH 10.6.

The virtualization and RISC-V items point at a project that still targets both server workloads and emerging architectures. The takeaway is simple: 8.0 modernizes the platform's hardware support without changing its release rhythm.

Why does the address space change matter?

The kernel virtual address space defines how much memory, including video RAM, the kernel can map at once. On AMD64, OpenBSD previously capped this at 4 GB. Graphics cards with larger memory pools forced awkward workarounds, and modern cards routinely exceed that budget.

Raising the ceiling to 512 GB removes the constraint for the foreseeable lifetime of any current GPU. Combined with the new Intel Arc support, the change makes OpenBSD a more realistic option on contemporary desktop and workstation hardware. In plain terms, the system can now see and use the memory that today's graphics cards actually carry.

How does the security record hold up?

De Raadt's quoted claim spans the project's full history since the 1996 fork from NetBSD. Two remote holes in the default install across that period remains the figure the project itself stands behind, and 8.0 keeps the default-install discipline that underpins it. The bundled crypto and remote-access stack moves forward in step, with LibreSSL 4.4.0 and OpenSSH 10.6 both receiving security and internal improvements.

The RPKI-to-router daemon, rtrd(8), adds a piece of routing security infrastructure that network operators can deploy directly from the base system. The takeaway: the security posture that defines the project stays intact, and the base system keeps absorbing roles that previously required third-party tools.

What comes next for the platform?

The semiannual schedule means the next release is already on a predictable clock, roughly six months out. The pattern in 8.0 — wider GPU support, a larger address space, deeper RISC-V and ARM64 work, and a stronger virtualization stack — suggests the next cycle will continue pushing OpenBSD toward modern hardware rather than retreat to legacy niches. How far the Intel Arc support matures, and whether the 64-vCPU guest limit draws more server deployments, will be the items to watch when the next release lands.

Original: en.wikipedia.org

Share this article:

More from Tom Whitfield

Tom Whitfield

Show full bio

Staff writer covering companies, deals and strategy in Semiconductors, chip manufacturing, hardware, AI compute at Chip Dispatch.

685 articles

Related articles

« Previous article