29:27
 | It has been suggested that this article be merged with OpenBSD Foundation. (Discuss) Proposed since May 2021. |
 Free, Functional, and Secure | |
 OpenBSD 6.1 default desktop with various utilities: top, xterm, xclock, xcalc, glxgears | |
| Developer | The OpenBSD Project |
|---|---|
| Written in | C, assembly, Perl, Unix shell |
| OS family | Unix-like |
| Working state | Current |
| Source model | Open source |
| Initial release | July 1996 |
| Latest release | 6.9 (1 May 2021) [±] |
| Repository |  |
| Package manager | OpenBSD package tools[1] |
| Platforms | Alpha, x86-64, ARMv7, ARMv8 (64-bit), PA-RISC, IA-32, LANDISK, Omron LUNA-88K, Loongson, MIPS64, PowerPC, SPARC64[2] |
| Kernel type | Monolithic |
| Userland | BSD |
| Default user interface | Modified pdksh, X11 (FVWM) |
| License | BSD, ISC, other permissive licenses[3] |
| Official website | www |
OpenBSD is a security-focused, free and open-source, Unix-like operating system based on the Berkeley Software Distribution (BSD). Theo de Raadt created OpenBSD in 1995 by forking NetBSD. According to the website, the OpenBSD project emphasizes "portability, standardization, correctness, proactive security and integrated cryptography."[4]
The OpenBSD project maintains portable versions of many subsystems as packages for other operating systems. Because of the project's preferred BSD license, many components are reused in proprietary and corporate-sponsored software projects. The firewall code in Apple's macOS is based on OpenBSD's PF firewall code,[5]Android's Bionic C standard library is based on OpenBSD code,[6]LLVM uses OpenBSD's regular expression library,[7] and Windows 10 uses OpenSSH (OpenBSD Secure Shell) with LibreSSL.[8]
The word "open" in the name OpenBSD refers to the availability of the operating system's source code on the Internet, although the word "open" in the name OpenSSH means "OpenBSD". It also refers to the wide range of hardware platforms the system supports.[9]
In December 1994, Theo de Raadt, a founding member of the NetBSD project, was asked to resign from the NetBSD core team.[11][12] 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.[13] Since then, the project has issued a release every six months, each of which is supported for one year.
On 25 July 2007, OpenBSD developer Bob Beck announced the formation of the OpenBSD Foundation, a Canadian non-profit organization formed to "act as a single point of contact for persons and organizations requiring a legal entity to deal with when they wish to support OpenBSD."[14]
It is hard to determine how widely OpenBSD is used, because the developers do not publish or collect usage statistics. In September 2005, the BSD Certification Group surveyed BSD users, showing that 33 percent used OpenBSD,[10] behind FreeBSD with 77 percent and ahead of NetBSD with 16 percent.[n 1]
OpenBSD features a robust TCP/IP networking stack, and can be used as a router[15] or wireless access point.[16] OpenBSD's security enhancements, built-in cryptography, and packet filter make it suitable for security purposes such as firewalls,[17]intrusion-detection systems, and VPN gateways.
Several proprietary systems are based on OpenBSD, including devices from Armorlogic (Profense web application firewall), Calyptix Security,[18] GeNUA,[19] RTMX,[20] and .vantronix.[21]
Some versions of Microsoft's Services for UNIX, an extension to the Windows operating system to provide Unix-like functionality, use much OpenBSD code included in the Interix interoperability suite,[22][23] developed by Softway Systems Inc., which Microsoft acquired in 1999.[24][25] Core Force, a security product for Windows, is based on OpenBSD's pf firewall.[26]
OpenBSD ships with Xenocara,[27] an implementation of the X Window System, and is suitable as a desktop operating system for personal computers, including laptops.[28][29]:xl As of September 2018[update], OpenBSD includes approximately 8000 packages in its software repository,[30] including desktop environments such as GNOME, Plasma 4, and Xfce, and web browsers such as Firefox and Chromium.[31] The project also includes three window managers in the main distribution: cwm, FVWM (part of the default configuration for Xenocara), and twm.[32]
OpenBSD features a full server suite and can be configured as a mail server, web server, FTP server, DNS server, router, firewall, NFS file server, or any combination of these.
Shortly after OpenBSD was created, De Raadt was contacted by a local security software company named Secure Networks (later acquired by McAfee).[33][34] They were developing a network security auditing tool called Ballista,[n 2] which was intended to find and exploit software security flaws. This coincided with De Raadt's interest in security, so the two cooperated leading up to the release of OpenBSD 2.3.[35] This collaboration helped to define security as the focus of the OpenBSD project.[36]
OpenBSD includes numerous features designed to improve security, such as:
strlcat for strcat and strlcpy for strcpy[37]To reduce the risk of a vulnerability or misconfiguration allowing privilege escalation, many programs have been written or adapted to make use of privilege separation, privilege revocation and chrooting. Privilege separation is a technique, pioneered on OpenBSD and inspired by the principle of least privilege, where a program is split into two or more parts, one of which performs privileged operations and the other—almost always the bulk of the code—runs without privilege.[41] Privilege revocation is similar and involves a program performing any necessary operations with the privileges it starts with then dropping them. Chrooting involves restricting an application to one section of the file system, prohibiting it from accessing areas that contain private or system files. Developers have applied these enhancements to OpenBSD versions of many common applications, such as tcpdump, file, tmux, smtpd, and syslogd.[42]
OpenBSD developers were instrumental in the creation and development of OpenSSH (aka OpenBSD Secure Shell), which is developed in the OpenBSD CVS repositories. OpenBSD Secure Shell is based on the original SSH.[43] It first appeared in OpenBSD 2.6 and is now by far the most popular SSH client and server, available on many operating systems.[44]
The project has a policy of continually auditing source code for problems, work that developer Marc Espie has described as "never finished ... more a question of process than of a specific bug being hunted." He went on to list several typical steps once a bug is found, including examining the entire source tree for the same and similar issues, "try[ing] to find out whether the documentation ought to be amended", and investigating whether "it's possible to augment the compiler to warn against this specific problem."[45]
The OpenBSD website features a prominent reference to the system's security record. Until June 2002, it read:
Five years without a remote hole in the default install!
In June 2002, Mark Dowd of Internet Security Systems disclosed a bug in the OpenSSH code implementing challenge–response authentication.[46] This vulnerability in the OpenBSD default installation allowed an attacker remote access to the root account, which was extremely serious not only to OpenBSD, but also to the large number of other operating systems that were using OpenSSH by that time.[47] This problem necessitated the adjustment of the slogan on the OpenBSD website to:
One remote hole in the default install, in nearly 6 years!
The quote remained unchanged as time passed, until on March 13, 2007, when Alfredo Ortega of Core Security Technologies[48] disclosed a network-related remote vulnerability.[49] The quote was subsequently changed to:
Only two remote holes in the default install, in a heck of a long time!
This statement has been criticized because the default install contains few running services, and many use cases require additional services.[50] Also, because the ports tree contains unaudited third-party software, it is easy for users to compromise security by installing or improperly configuring packages. However, the project maintains that the slogan is intended to refer to a default install and that it is correct by that measure.
One of the fundamental ideas behind OpenBSD is a drive for systems to be simple, clean, and secure by default. The default install is quite minimal, which the project states is to ensure novice users "do not need to become security experts overnight",[51] which fits with open-source and code auditing practices considered important elements of a security system.[52]
On 11 December 2010, Gregory Perry, a former technical consultant for the Federal Bureau of Investigation (FBI), emailed De Raadt alleging that the FBI had paid some OpenBSD ex-developers 10 years prior to insert backdoors into the OpenBSD Cryptographic Framework. De Raadt made the email public on 14 December by forwarding it to the openbsd-tech mailing list and suggested an audit of the IPsec codebase.[53][54] De Raadt's response was skeptical of the report and he invited all developers to independently review the relevant code. In the weeks that followed, bugs were fixed but no evidence of backdoors was found.[55] De Raadt stated "I believe that NetSec was probably contracted to write backdoors as alleged. If those were written, I don't believe they made it into our tree. They might have been deployed as their own product."[56]
In December 2017, Ilja van Sprundel, director at IOActive, gave a talk at the CCC[57] as well as DEF CON,[58] entitled "Are all BSDs created equally? — A survey of BSD kernel vulnerabilities.", in which he stated that although OpenBSD was the clear winner of the BSDs in terms of security, "Bugs are still easy to find in those kernels, even in OpenBSD".
Two years later, in 2019, a talk named "A systematic evaluation of OpenBSD’s mitigations" was given[59] at the CCC, arguing that while OpenBSD has some effective mitigations, a significant part of them are "useless at best and based on pure luck and superstition", arguing for a more rational approach when it comes to designing them.[60]
Supported platforms and devices are listed in the OpenBSD Supported Platforms Notes.[61] Other configurations may also work, but simply have not been tested or documented yet. Rough automatically extracted lists of supported device ids are available in a third party repository.[62]
In 2020, a new project was introduced to automatically collect information about tested hardware configurations.[63]
Many open source projects started as components of OpenBSD, including:
Some subsystems have been integrated into other BSD operating systems,[72][73][74] and many are available as packages for use in other Unix-like systems.[75][76][77]
Linux administrator Carlos Fenollosa commented on moving from Linux to OpenBSD that the system is faithful to the Unix philosophy of small, simple tools that work together well: "Some base components are not as feature-rich, on purpose. Since 99% of the servers don't need the flexibility of Apache, OpenBSD's httpd will work fine, be more secure, and probably faster".[78] He characterized the developer community's attitude to components as: "When the community decides that some module sucks, they develop a new one from scratch. OpenBSD has its own NTPd, SMTPd and, more recently, HTTPd. They work great".[78] As a result, OpenBSD is relatively prolific in creating components that become widely reused by other systems.
OpenBSD runs nearly all of its standard daemons within chroot and privsep security structures by default, as part of hardening the base system.[78]
The Calgary Internet Exchange was formed in 2012, in part to serve the needs of the OpenBSD project.[79]
OpenBSD includes a number of third-party components, many with OpenBSD-specific patches,[31] such as X.Org, Clang[80] (the default compiler on several architectures), GCC,[38][n 3]Perl, NSD, Unbound, ncurses, GNU binutils, GDB, and AWK.
Development is continuous, and team management is open and tiered. Anyone with appropriate skills may contribute, with commit rights being awarded on merit and De Raadt acting as coordinator.[29]:xxxv Two official releases are made per year, with the version number incremented by 0.1,[81] and these are each supported for twelve months (two release cycles).[82] Snapshot releases are also available at frequent intervals.
Maintenance patches for supported releases may be applied manually or by updating the system against the patch branch of the CVS repository for that release.[83] Alternatively, a system administrator may opt to upgrade using a snapshot release and then regularly update the system against the -current branch of the CVS repository, in order to gain pre-release access to recently added features.
The generic OpenBSD kernel provided by default is strongly recommended for end users, in contrast to operating systems that recommend user kernel customization.[84]
Packages outside the base system are maintained by CVS through a ports tree and are the responsibility of the individual maintainers, known as porters. As well as keeping the current branch up to date, porters are expected to apply appropriate bug-fixes and maintenance fixes to branches of their package for OpenBSD's supported releases. Ports are generally not subject to the same continuous auditing as the base system due to lack of manpower.
Binary packages are built centrally from the ports tree for each architecture. This process is applied for the current version, for each supported release, and for each snapshot. Administrators are recommended to use the package mechanism rather than build the package from the ports tree, unless they need to perform their own source changes.
OpenBSD's developers regularly meet at special events called hackathons,[85] where they "sit down and code", emphasizing productivity.[86]
Most new releases include a song.[87]
OpenBSD is known for its high-quality documentation.[88][89]
When OpenBSD was created, De Raadt decided that the source code should be available for anyone to read. At the time, a small team of developers generally had access to a project's source code.[90] Chuck Cranor[91] and De Raadt concluded this practice was "counter to the open source philosophy" and inconvenient to potential contributors. Together, Cranor and De Raadt set up the first public, anonymous CVS server. De Raadt's decision allowed users to "take a more active role", and established the project's commitment to open access.[90]
OpenBSD does not include closed source binary drivers in the source tree, nor do they include code requiring the signing of non-disclosure agreements.[92]
Since OpenBSD is based in Canada, no United States export restrictions on cryptography apply, allowing the distribution to make full use of modern algorithms for encryption. For example, the swap space is divided into small sections and each section is encrypted with its own key, ensuring that sensitive data does not leak into an insecure part of the system.[17]
OpenBSD randomizes various behaviors of applications, making them less predictable and thus more difficult to attack. For example, PIDs are created and associated randomly to processes; the bind system call uses random port numbers; files are created with random inode numbers; and IP datagrams have random identifiers.[93] This approach also helps expose bugs in the kernel and in user space programs.
The OpenBSD policy on openness extends to hardware documentation: in the slides for a December 2006 presentation, De Raadt explained that without it "developers often make mistakes writing drivers", and pointed out that "the [oh my god, I got it to work] rush is harder to achieve, and some developers just give up."[94] He went on to say that vendor-supplied binary drivers are unacceptable for inclusion in OpenBSD, that they have "no trust of vendor binaries running in our kernel" and that there is "no way to fix [them] ... when they break."[94]
OpenBSD maintains a strict license policy,[3] preferring the ISC license and other variants of the BSD license. The project attempts to "maintain the spirit of the original Berkeley Unix copyrights," which permitted a "relatively un-encumbered Unix source distribution."[3] The widely used Apache License and GNU General Public License are considered overly restrictive.[95]
In June 2001, triggered by concerns over Darren Reed's modification of IPFilter's license wording, a systematic license audit of the OpenBSD ports and source trees was undertaken.[96] Code in more than a hundred files throughout the system was found to be unlicensed, ambiguously licensed or in use against the terms of the license. To ensure that all licenses were properly adhered to, an attempt was made to contact all the relevant copyright holders: some pieces of code were removed, many were replaced, and others, such as the multicast routing tools mrinfo and map-mbone, were relicensed so that OpenBSD could continue to use them.[97][98] Also removed during this audit was all software produced by Daniel J. Bernstein. At the time, Bernstein requested that all modified versions of his code be approved by him prior to redistribution, a requirement to which OpenBSD developers were unwilling to devote time or effort.[99][100][101]
Because of licensing concerns, the OpenBSD team has reimplemented software from scratch or adopted suitable existing software. For example, OpenBSD developers created the PF packet filter after unacceptable restrictions were imposed on IPFilter. PF first appeared in OpenBSD 3.0[102] and is now available in many other operating systems.[103] OpenBSD developers have also replaced GPL-licensed tools (such as CVS, diff, grep and pkg-config) with permissively licensed equivalents.[104][105]
Although the operating system and its portable components are used in commercial products, De Raadt says that little of the funding for the project comes from the industry: "traditionally all our funding has come from user donations and users buying our CDs (our other products don't really make us much money). Obviously, that has not been a lot of money."[81]
For a two-year period in the early 2000s, the project received funding from DARPA, which "paid the salaries of 5 people to work completely full-time, bought about $30k in hardware, and paid for 3 hackathons", from the POSSE project.[81]
In 2006, the OpenBSD project experienced financial difficulties.[106] The Mozilla Foundation[107] and GoDaddy[108] are among the organizations that helped OpenBSD to survive. However, De Raadt expressed concern about the asymmetry of funding: "I think that contributions should have come first from the vendors, secondly from the corporate users, and thirdly from individual users. But the response has been almost entirely the opposite, with almost a 15-to-1 dollar ratio in favor of the little people. Thanks a lot, little people!"[81]
On 14 January 2014, Bob Beck issued a request for funding to cover electrical costs. If sustainable funding was not found, Beck suggested the OpenBSD project would shut down.[109] The project soon received a US$20,000 donation from Mircea Popescu, the Romanian creator of the MPEx bitcoin stock exchange, paid in bitcoins.[110] The project raised US$150,000[111] in response to the appeal, enabling it to pay its bills and securing its short-term future.[110] Since 2014, several large contributions to the OpenBSD Foundation have come from corporations such as Microsoft,[112] Facebook, and Google as well as the Core Infrastructure Initiative.[113]
During the 2016 and 2017 fundraising campaigns, Smartisan, a Chinese company, was the leading financial contributor to the project.[114][115]
OpenBSD is freely available in various ways: the source can be retrieved by anonymous CVS,[116] and binary releases and development snapshots can be downloaded by FTP, HTTP, and rsync.[117] Prepackaged CD-ROM sets through version 6.0 can be ordered online for a small fee, complete with an assortment of stickers and a copy of the release's theme song. These, with their artwork and other bonuses, have been one of the project's few sources of income, funding hardware, Internet service, and other expenses.[118] Beginning with version 6.1, CD-ROM sets are no longer released.
OpenBSD provides a package management system for easy installation and management of programs which are not part of the base operating system.[119] Packages are binary files which are extracted, managed and removed using the package tools. On OpenBSD, the source of packages is the ports system, a collection of Makefiles and other infrastructure required to create packages. In OpenBSD, the ports and base operating system are developed and released together for each version: this means that the ports or packages released with, for example, 4.6 are not suitable for use with 4.5 and vice versa.[119]
Initially, OpenBSD used a haloed version of the BSD daemon mascot drawn by Erick Green, who was asked by De Raadt to create the logo for the 2.3 and 2.4 versions of OpenBSD. Green planned to create a full daemon, including head and body, but only the head was completed in time for OpenBSD 2.3. The body as well as pitchfork and tail was completed for OpenBSD 2.4.[120]
Subsequent releases used variations such as a police daemon by Ty Semaka,[121] but eventually settled on a pufferfish named Puffy.[122] Since then, Puffy has appeared on OpenBSD promotional material and featured in release songs and artwork.
The promotional material of early OpenBSD releases did not have a cohesive theme or design, but later the CD-ROMs, release songs, posters and tee-shirts for each release have been produced with a single style and theme, sometimes contributed to by Ty Semaka of the Plaid Tongued Devils.[87] These have become a part of OpenBSD advocacy, with each release expounding a moral or political point important to the project, often through parody.[123]
Themes have included Puff the Barbarian in OpenBSD 3.3, which included an 80s rock song and parody of Conan the Barbarian alluding to open documentation,[87]The Wizard of OS in OpenBSD 3.7, related to the project's work on wireless drivers, and Hackers of the Lost RAID, a parody of Indiana Jones referencing the new RAID tools in OpenBSD 3.8.
RTMX O/S is a product extension to OpenBSD Unix-like operating system with emphasis on embedded, dedicated applications.
The Next Generation Firewall is not a standalone device, it is a Router for operation in security critical environments with high requirements for availability, comprehensive support as well as reliable and trusted systems powered by OpenBSD.
CORE FORCE provides inbound and outbound stateful packet filtering for TCP/IP protocols using a Windows port of OpenBSD's PF firewall, granular file system and registry access control and programs' integrity validation.
OpenBSD ships with the cwm(1), fvwm(1) and twm(1) window managers, [...]
Without [SNI's] support at the right time, this release probably would not have happened.
Privilege separation: [...] The concept is now used in many OpenBSD programs, for example [...] etc.
Secure by Default.
This is the port of OpenBSD's excellent OpenSSH to Linux and other Unices.
This is the port of OpenBSD's excellent OpenSSH to Linux and other Unices.
I also hosted and helped create the first Anonymous CVS server on the Internet (the original anoncvs.openbsd .org [...]
Integrate good code from any source with acceptable licenses. [...], NDAs are never acceptable.
New license from Xerox! This code is now FREE! Took a while and a lot of mails, but it is worth it.
New license from Xerox! This code is now FREE! Took a while and a lot of mails, but it is worth it.
OpenBSD 2.5 introduces the new Cop daemon image done by cartoonist Ty Semeka.
Each OpenBSD release has a graphical theme and a song that goes with it. The theme reflects a major concern that the OpenBSD programmers are addressing or bringing to light.
By: Wikipedia.org
Edited: 2021-06-18 18:44:44
Source: Wikipedia.org
