OpenBSD

OpenBSD Security Views

OpenBSD believes very strongly in strong security. We believe that we are NUMBER ONE in the industry at the moment. Due to our open software development model, we are able to take a more uncompromising view towards increasing security than Sun, SGI, IBM, HP, or other vendors are able to.

Our security auditing team typically has between six and twelve members, and most of us continually search for and fix security holes. We have been auditing for approximately two years. The process we followed to increase security was simply a comprehensive file-by-file analysis of every critical software component. Flaws were found in just about every area of the system. Entire new classes of security problems were found while we were doing the audit, and in many cases source code which had been audited earlier had to be re-audited with these new flaws in mind.

The process is not over yet, and as you can see we continue to find and fix new security flaws.

OpenBSD 2.1 Security Advisories

These are the OpenBSD 2.1 advisories. All these problems are solved in OpenBSD 2.2. Some of these problems still exist in other operating systems.

OpenBSD 2.2 Security Advisories

These are the OpenBSD 2.2 advisories. All these problems are solved in OpenBSD current. Some of these problems still exist in other operating systems. Patches are provided

Other Resources

Other security advisories that have (in the past) affected OpenBSD can be found at the Secure Networks archive.

If you find a new security problem, you can mail it to deraadt@openbsd.org.
If you wish to PGP encode it (but please only do so if privacy is very urgent, since it is inconvenient) use this pgp key.