The FreeBSD Foundation Funds OpenSSH Portability Fixes and Intel Wi-Fi Driver Work
How the FreeBSD Foundation's sponsored-development model paid for real, shipped improvements to OpenSSH compatibility and the iwlwifi driver stack rather than just donating money in the abstract.
The FreeBSD Foundation — the US 501(c)(3) nonprofit that funds development, infrastructure, and advocacy work for the FreeBSD Project — doesn’t just write checks in the abstract. Its sponsored-development model pays specific developers to work on specific, scoped pieces of the system, and two efforts in particular show what that actually looks like in practice: keeping OpenSSH working correctly on FreeBSD, and modernizing FreeBSD’s notoriously uneven Wi-Fi support.
OpenSSH isn’t a FreeBSD project, but it has to work on FreeBSD
OpenSSH itself is maintained by the OpenBSD Project, not FreeBSD — but every BSD and Linux distribution that ships OpenSSH relies on “portable OpenSSH,” a version adapted to build and run correctly across operating systems well beyond OpenBSD itself. That portability work doesn’t happen automatically just because the upstream code is open source; someone has to actually track down and fix the platform-specific issues that appear when a new OpenSSH release meets a specific FreeBSD version’s specific libc, PAM stack, or kernel interfaces.
The FreeBSD Foundation sponsored exactly this kind of work for OpenSSH releases 9.2p1 and 9.3p1 — funding the fixes and updates needed to get those specific portable OpenSSH releases building and running correctly on FreeBSD, rather than leaving that adaptation work to happen only if a volunteer happened to pick it up unprompted. It’s a narrow, unglamorous category of work, and that’s exactly why sponsorship matters for it — the alternative isn’t “someone volunteers eventually,” it’s “FreeBSD’s OpenSSH support lags behind or breaks until someone finds time,” for a piece of software that essentially every FreeBSD server depends on for remote access.
Wi-Fi: a much longer-standing weak spot
FreeBSD’s wireless networking support has lagged Linux’s for years, for reasons that are structural rather than a simple lack of effort — wireless chipset vendors overwhelmingly prioritize Linux driver support, and building or maintaining FreeBSD equivalents means either reverse-engineering behavior or porting driver logic from Linux or OpenBSD codebases with meaningfully different kernel APIs to target.
The FreeBSD Foundation began directly funding developers to work on this specifically, including Björn Zeeb and Tom Jones on broader wireless usability. In November 2023, the Foundation funded a specific, scoped effort on the iwlwifi driver — the driver stack covering a large share of Intel’s Wi-Fi chipsets — led by developer Cheng Cui in collaboration with Zeeb. That effort continued into a broader “Laptop Support and Usability Improvements Project,” which launched at the end of 2024 and consolidated ongoing work across Wi-Fi, audio, and accessibility, alongside modernized graphics and power-management support — the kind of coordinated, multi-area push toward “FreeBSD as a usable laptop OS” that’s hard to sustain purely on volunteer time, since it requires the same people staying focused across several interlocking areas over an extended period rather than picking up isolated patches opportunistically.
What sponsored development actually buys
The throughline across both efforts is the same: neither OpenSSH portability patches nor a modern Intel Wi-Fi driver are the kind of high-visibility, exciting features that attract volunteer contributors on their own — they’re maintenance and modernization work that matters enormously to whether FreeBSD is actually usable in practice, and that’s precisely the category of work the Foundation’s funding model is designed to guarantee gets done on a reliable schedule, rather than leaving it to chance.
Sources: