openbsd.org

OpenBSD is a free, multi-platform, 4.4BSD-based UNIX-like operating system whose stated emphasis is portability, standardization, correctness, proactive security, and integrated cryptography. If your hardware appears on its supported platform list and your use case fits a general-purpose UNIX-like system, it is a reasonable candidate; if you need a specific commercial application or vendor-certified stack, check that first. Help is available through the project's own documentation (FAQ, manual pages, patches, problem reporting) plus mailing lists, user groups, and commercial support.

What OpenBSD is, in the project's own terms

The openbsd.org site describes the project as producing a free, multi-platform 4.4BSD-based UNIX-like operating system. Its stated priorities are:

• Portability
• Standardization
• Correctness
• Proactive security
• Integrated cryptography

The site notes that OpenSSH originated in OpenBSD, as an example of the project's wider effect. The current release listed is OpenBSD 7.9, released May 19, 2026, described as the 60th release. Development is done entirely by volunteers, and developer events and the development environment are funded through contributions collected by The OpenBSD Foundation.

Checking whether your hardware is supported

The site's navigation includes a Hardware Platforms entry, which is the page to consult before committing to an install. The practical check is:

1. Identify your machine's architecture (for example, the CPU family and whether it is 64-bit).
2. Open the Hardware Platforms page from openbsd.org and confirm your platform is listed.
3. If it is listed, review the platform-specific notes for known limitations before installing.

Because OpenBSD is described as multi-platform and portability-focused, support is broad rather than tied to one vendor's hardware. That said, "multi-platform" does not mean every device works: peripherals, wireless chipsets, and graphics hardware are the usual places where a listed platform still has gaps. The platform page and the FAQ are where those details live.

Matching OpenBSD to a use case

OpenBSD's own framing points to where it fits best:

The site also carries a well-known claim about the default install: "Only two remote holes in the default install, in a heck of a long time!" Read it precisely — it is a statement about the default install over the project's history, not a guarantee that any configured system is unbreakable. Once you add services, users, and third-party software, your exposure depends on that configuration, not on the default.

If your use case depends on a specific proprietary application, a vendor support contract for the OS itself, or hardware that is not on the platform list, verify those points before deploying.

Where to get OpenBSD and its source

The site provides two paths:

• Download — for the released system.
• Getting Source — for the source tree, with these access routes listed: AnonCVS, CVSWeb, GitHub Mirror, and GotHub Mirror.

The project states OpenBSD is freely available from its download sites. The site does not present pricing or account requirements for these downloads; treat any login or mirror-specific condition as something to confirm on the page you actually use rather than assuming.

Where to get help when something goes wrong

The site's resource list maps directly onto the kinds of problems you will hit:

• FAQ — start here for common configuration and setup questions.
• Manual Pages — the authoritative reference for commands and configuration files.
• Changelog — what changed between releases.
• Patches — fixes to apply.
• Reporting Problems — the project's channel for submitting a bug report.
• Mailing Lists — community discussion and searchable archives.
• User Groups — local, in-person help.
• Commercial Support — paid options if you need a contractual relationship.
• Events and Papers, Hackathons — talks and development gatherings.

A workable order when you are stuck: check the manual page for the specific tool, then the FAQ, then search the mailing list archives, and only then post a question or file a problem report. For a bug report, the Reporting Problems page tells you what information the developers need — following it is what makes the report actionable.

Supporting the project

If you want to contribute financially, the site lists Donations, Art, Merchandise, and The OpenBSD Foundation. Contributions, per the site, keep OpenBSD "a vibrant and free operating system" and fund the development environment and developer events.

OpenBSD is developed entirely by volunteers, and its development environment and developer events are funded through contributions collected by The OpenBSD Foundation. If you want to support the project, the openbsd.org site points to several concrete channels: donations, merchandise, mailing lists, hackathons, user groups, and commercial support. The project itself is not presented as a company product; the site describes it as a free, multi-platform 4.4BSD-based UNIX-like operating system, with the current release listed as OpenBSD 7.9 (released May 19, 2026, the 60th release).

Who develops OpenBSD

The main page states plainly that OpenBSD is developed entirely by volunteers. That matters for how you interpret the project:

• There is no commercial vendor presented as owning or directing development.
• The work is distributed across contributors rather than a single company.
• The project emphasizes portability, standardization, correctness, proactive security, and integrated cryptography.

A useful example of the project's reach: OpenSSH, widely used for secure remote access, comes from OpenBSD. So even if you never install OpenBSD itself, you may already depend on code that originated in this volunteer-driven project.

How the project is funded

Funding is separated from development. According to the site, the project's development environment and developer events are funded through contributions collected by The OpenBSD Foundation. Contributions, in the project's own framing, ensure OpenBSD remains a vibrant and free operating system.

That structure tells you what your money supports: infrastructure and in-person developer events, not a corporate payroll. It also means the project's continuity depends on ongoing contributions rather than product revenue.

How individuals can support or participate

The site lists multiple ways to engage, and they serve different levels of involvement.

If your goal is simply to use OpenBSD, you do not need to participate in any of these. If your goal is to sustain the project, donations and merchandise are the direct routes. If your goal is to contribute technically, mailing lists and hackathons are the entry points the site surfaces.

What this means for you

• As a user: OpenBSD is freely available from the project's download sites, and the site provides downloads, source, changelog, FAQ, manual pages, and patches.
• As a contributor: Start with the mailing lists and look at hackathons; the project is volunteer-run, so participation is the development model, not an add-on.
• As a supporter: Donations and merchandise go through the channels listed on the site; the Foundation is the named funding body.
• As an organization: If you need guaranteed help rather than community support, the site lists commercial support as a separate option.

The security reputation attached to OpenBSD — the site notes "only two remote holes in the default install, in a heck of a long time" — is a product of this volunteer project's stated priorities, not of a vendor's marketing department. Understanding who develops and funds it explains why the project's resources, events, and support paths are organized the way they are.

OpenBSD's security reputation rests on a specific, checkable claim on its homepage: "Only two remote holes in the default install, in a heck of a long time!" That statement refers to remotely exploitable vulnerabilities in a default installation over the project's history — not to zero vulnerabilities, and not to a system that is automatically secure regardless of how you configure it. The project describes its emphasis as "portability, standardization, correctness, proactive security and integrated cryptography," which is a design philosophy rather than a product guarantee.

What the project actually claims

The homepage makes three distinct points that are worth separating:

• A track record claim: two remote holes in the default install over a long period. The qualifiers matter — "remote" (not local privilege escalation), "default install" (not a heavily customized system), and "in a heck of a long time" (a deliberately informal timeframe).
• A design claim: proactive security and integrated cryptography are stated project goals, listed alongside portability and correctness rather than as an afterthought.
• A provenance claim: OpenSSH, the widely used secure shell software, originated in OpenBSD. This is offered as evidence that the project's security work has had effects beyond its own operating system.

None of these claims assert that OpenBSD is unbreakable. They describe priorities and a historical record.

Where the security reputation comes from

Proactive rather than reactive security

The distinction the project draws is between fixing problems after they are exploited and building defenses into the code and defaults beforehand. In practice this shows up as an emphasis on code correctness and auditing, since many vulnerabilities originate in ordinary programming mistakes rather than exotic attacks.

Integrated cryptography

Cryptography is described as integrated rather than bolted on. The OpenSSH example illustrates why this matters: a cryptographic tool that ships as part of the base system, maintained by the same project, avoids the version drift and configuration gaps that appear when security software is added separately.

Default hardening

The claim is specifically about the default install. That framing implies the shipped configuration is intended to be reasonably safe without the user first performing a hardening checklist. This is a meaningful difference from systems where security depends heavily on post-installation tuning.

What the claim does not mean

A "remote hole" is a vulnerability exploitable over a network without prior access. Local privilege escalation, misconfiguration, and vulnerabilities in third-party software you add are outside the scope of that specific sentence. Reading it as "OpenBSD cannot be compromised" overstates what is being asserted.

How to evaluate the claim for yourself

Because the homepage statement is a summary, the underlying material is where the specifics live. The site's own resources point to the places to look:

• FAQ — explains configuration and operational practices, including the reasoning behind defaults.
• Manual pages — document how individual components actually behave.
• Patches — the record of what has been fixed and when, which is the most direct way to check the security history rather than take the summary on faith.
• Changelog — tracks changes across releases.
• Reporting Problems — the channel through which issues are surfaced and handled.

The current release listed on the site is OpenBSD 7.9, released May 19, 2026, described as the 60th release. Security claims should be read against a specific release and its patch history, not as a permanent property of the name.

Who this matters for

The security positioning is most relevant if you are choosing an operating system where you want safe defaults and cryptographic tooling present from the start, and you are willing to work within the project's conventions rather than assume security is automatic. It is less useful as a reason to skip configuration review, patch tracking, or the ordinary operational work that any networked system requires.

For a concrete check: pick the release you intend to run, read its entry in the patches and changelog pages, and confirm that the defaults described in the FAQ match how you plan to deploy it. That turns a reputation into something you have verified for your own case.

OpenBSD is a free, multi-platform, 4.4BSD-based UNIX-like operating system produced by the OpenBSD project, and openbsd.org is that project's main page. The site is the starting point for downloading the OS, getting the source code, reading documentation, reporting problems, and supporting the project. If you want to know what the project stands for and where to find its official resources, this page is the canonical entry point.

What OpenBSD is

According to the project's own description, OpenBSD is developed entirely by volunteers. Its stated emphases are:

• Portability — running across many hardware platforms
• Standardization and correctness
• Proactive security
• Integrated cryptography

The project is also the origin of widely used software: OpenSSH comes from OpenBSD. The site highlights the claim of "only two remote holes in the default install, in a heck of a long time," which reflects the project's security-focused reputation.

What the website provides

The main page organizes the project's resources into a few clear areas:

Release and licensing facts

• The current release listed on the site is OpenBSD 7.9, released May 19, 2026 — the 60th release.
• OpenBSD is described as freely available from the project's download sites.
• Development is done by volunteers; the development environment and developer events are funded through contributions collected by The OpenBSD Foundation.

How to use the site

1. To try or install OpenBSD — start at Getting OpenBSD and download from the official sites.
2. To read the source — use Getting Source, which offers AnonCVS, CVSWeb, and GitHub/GotHub mirrors.
3. To learn the system — go to Resources for the FAQ and Manual Pages; the Changelog tracks changes.
4. To report a bug — use Reporting Problems and check Patches for existing fixes.
5. To get help or give support — Mailing Lists for community discussion, Commercial Support for paid options, and Supporting OpenBSD if you want to donate or buy merchandise.

The site does not state pricing for support or merchandise on the main page, so check the linked pages for current details.

The openbsd.org homepage gives you two separate starting points: Getting OpenBSD for installation images and Getting Source for the source tree. Use the first if you want to install or run the system, and the second if you want to read, build, or track the code. Before downloading, check that the release and hardware platform match what you need — the site lists the current release and the supported platforms.

Downloading OpenBSD

The homepage links to Download and Getting OpenBSD, which lead to the official download sites. The page states that OpenBSD is freely available from those sites and that the current release is OpenBSD 7.9, released May 19, 2026 — the 60th release.

Steps:

1. Open the Getting OpenBSD entry from the homepage.
2. Confirm you are looking at the current release (7.9 at the time of the site text).
3. Pick the platform that matches your hardware. The site maintains a Hardware Platforms section describing supported platforms, so check it before choosing an image.
4. Download from an official download site rather than a third-party mirror.

Expected result: you have an installation image for a supported platform and a known release version. A common snag is grabbing an image for the wrong architecture or an older release; the release number and platform name are the two things to verify first.

Getting the source code

The homepage provides a Getting Source entry, and the source is reachable through several routes listed on the site:

Choose based on what you want to do:

• Just reading code or checking a file: CVSWeb or a mirror is the quickest path — no local setup.
• Tracking changes over time: AnonCVS gives you a working checkout you can update.
• Working with familiar tooling: the GitHub or GotHub mirrors fit workflows built around those platforms.

Expected result: you can view or check out the source. A common snag is treating a mirror as the authoritative tree — the project's own CVS infrastructure is the reference point, and mirrors are conveniences.

Supporting pages you will likely need

The homepage also links to material that answers most follow-up questions:

• FAQ — general questions about the system and project.
• Manual Pages — command and API reference.
• Patches and Reporting Problems — for fixes and bug reports.
• Changelog — what changed between releases.
• Mailing Lists — project discussion.
• Commercial Support — if you need paid help.

If installation or a build fails, the FAQ and manual pages are the first places to check before reporting a problem.

What the project is, in one line

OpenBSD is a free, multi-platform, 4.4BSD-based UNIX-like operating system. The project emphasizes portability, standardization, correctness, proactive security, and integrated cryptography, and it is developed entirely by volunteers. OpenSSH originated here. Development and developer events are funded through contributions collected by The OpenBSD Foundation, which is why the site also carries Donations, Art, and Merchandise links.