For years, Wine on OpenBSD was considered effectively impossible. The operating system's security model deliberately restricts setting the %gs segment register base — a hardware-level mechanism that Wine depends on to emulate Windows' thread-local storage. The conventional wisdom was that this architectural incompatibility was permanent. It wasn't. Andrii Zymohliad built a software-layer workaround that emulates the %gs prefix on instructions rather than trying to set gsbase directly. This is the kind of lateral engineering move that rewrites assumptions: instead of asking the kernel to relax a security boundary, the solution intercepts and translates the relevant instructions in userspace. The heavy lifting was shared between Zymohliad and Fabien, with Thomas Frohwein coordinating the port proposal and a small team of contributors testing and refining. The results are surprisingly functional. The team has tested several dozen 64-bit Windows applications, mostly successfully. Screenshots and livestreams show everything from Notepad++ to The Witcher 3's recently released remaster running on OpenBSD, the latter using vkd3d-proton for DirectX 12 translation. A livestream of The Witcher 3 reportedly runs better than the recording suggests, with the overhead coming from on-system ffmpeg capture rather than Wine itself. The limitations are honest and clearly stated. WoW64 — Windows' 32-bit compatibility layer — does not work, meaning legacy 32-bit Windows executables remain a dead end. Built-in Wine tests are disabled because they require X server access and several still hang, though this hasn't manifested as a problem in real-world application testing. The port is explicitly labeled run-at-your-own-risk, with the team recommending a separate non-privileged user account and exploring unveil(2) sandboxing for future hardening. What makes this notable beyond OpenBSD's niche is the timing. As Frohwein notes, the demand landscape has shifted: much Windows software has moved to 64-bit in the past decade, making a 64-bit-only Wine port far more useful than it would have been in 2015. The port arrives at precisely the moment when skipping 32-bit support costs the least. The development model here is pure volunteer open-source craft — a mailing list proposal with an attached tarball, credits to IRC handles and committer nicknames, tested on personal hardware. No corporate sponsor, no roadmap deck, no funding announcement. The thread references on openbsd-tech show the gsbase question being kicked around for months before the breakthrough. This is how infrastructure gets built when the people building it are also the people who need it. The port is now seeking 'ok?' from the OpenBSD ports community — the project's consensus-based approval process. If accepted, OpenBSD joins the small club of operating systems where Wine is a supported package, removing one of the last practical barriers for users who want both OpenBSD's security model and access to the Windows software ecosystem.
