"Free, Functional, and Secure"
|
|
OpenBSD 5.9 desktop
|
|
Developer | The OpenBSD Project |
---|---|
OS family | Unix-like (BSD) |
Working state | Current |
Source model | Open-source |
Initial release | 1 October 1996 |
Latest release | 6.0 (1 September 2016 | )
Package manager | OpenBSD package tools |
Platforms | Alpha, x86-64, ARMv7, PA-RISC, IA-32, , Omron LUNA-88K, MIPS64, PowerPC, and SPARC 64 |
Kernel type | Monolithic |
Userland | BSD |
Default user interface | Modified pdksh, FVWM X11 |
License | BSD, ISC, ATU, and other custom licenses |
Official website | www |
OpenBSD is a free and open source Unix-like computer operating system descended from Berkeley Software Distribution (BSD), a Research Unix derivative developed at the University of California, Berkeley. In late 1995, Theo de Raadt forked it from NetBSD. Besides the operating system as a whole, the project maintains portable versions of many subsystems, most notably OpenSSH, which are available as packages in other operating systems.
The project is known for its developers' insistence on open-source code, good documentation, code correctness, and security. It has strict policies on licensing, preferring the ISC license and other variants of the Simplified BSD License. Many of its security features are optional or absent in other operating systems. Its developers frequently audit the source tree for software bugs and security holes.
De Raadt coordinates the project from his home in Calgary, Alberta, Canada. Its logo and mascot is a pufferfish named Puffy.
In December 1994, NetBSD co-founder Theo de Raadt was asked to resign from his position as a senior developer and member of the NetBSD core team. The reason for this is not wholly clear, although there are claims that it was due to personality clashes within the NetBSD project and on its mailing lists.
In October 1995, de Raadt founded OpenBSD, a new project forked from NetBSD 1.0. The initial release, OpenBSD 1.2, was made in July 1996, followed by OpenBSD 2.0 in October of the same year. Since then, the project has followed a schedule of a release every six months, each of which is supported for one year.