OpenBSD

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by 200.127.1.208 (talk) at 00:20, 13 May 2007. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

OpenBSD
OpenBSD logo with Puffy, the pufferfish.
"Free, Functional & Secure"
DeveloperThe OpenBSD Project
OS familyBSD
Working stateCurrent
Source modelOpen source
Latest release4.1 / May 1, 2007
Repository
Package managerOpenBSD package tools and ports collection
PlatformsAMD64, Alpha, i386, MIPS, 68000, PowerPC, Sparc, Sparc64, VAX, Zaurus and others[1]
Kernel typeMonolithic
Default
user interface		Modified pdksh, FVWM 2.2.5 for X11
Official websitewww.openbsd.org

Template:Prerequisites header

! Computer and operating system |- ! Unix and Unix-like |- ! Software licensing |- ! Computer insecurity Template:Prerequisites footer

OpenBSD is a Unix-like computer operating system descended from Berkeley Software Distribution (BSD), a Unix derivative developed at the University of California, Berkeley. It was forked from NetBSD by project leader Theo de Raadt in late 1995. The project is widely known for the developers' insistence on open source code and quality documentation; uncompromising position on software licensing; and focus on security and code correctness. The project is coordinated from de Raadt's home in Calgary, Alberta, Canada. Its logo and mascot is Puffy, a pufferfish.

OpenBSD includes a number of security features absent or optional in other operating systems and has a tradition of developers auditing the source code for software bugs and security problems. The project maintains strict policies on licensing and prefers the open source BSD licence and its variants—in the past this has led to a comprehensive licence audit and moves to remove or replace code under licences found less acceptable.

As with most other BSD-based operating systems, the OpenBSD kernel and userland programs, such as the shell and common tools like cat and ps, are developed together in a single source repository. Third-party software is available as binary packages or may be built from source using the ports collection.

OpenBSD currently runs on 17 different hardware platforms, including the DEC Alpha, Intel i386, Hewlett-Packard PA-RISC, AMD AMD64 and Motorola 68000 processors, Apple's PowerPC machines, Sun SPARC and SPARC64-based computers, the VAX and the Sharp Zaurus.

History and popularity

See also: OpenBSD timeline
The OpenBSD 2.3 CD-ROM cover with the original mascot, before Puffy appeared with release 2.7

In December 1994, NetBSD co-founder Theo de Raadt was asked to resign his position as a senior developer and member of the NetBSD core team, and his access to the source code repository was revoked. 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.[2] De Raadt has been criticized for having a sometimes abrasive personality: in his book, Free For All, Peter Wayner claims that de Raadt "began to rub some people the wrong way" before the split from NetBSD;[3] Linus Torvalds has described him as "difficult;"[4] and an interviewer admits to being "apprehensive" before meeting him.[5] Many have different feelings: the same interviewer describes de Raadt's "transformation" on founding OpenBSD and his "desire to take care of his team," some find his straightforwardness refreshing, and few deny he is a talented coder[6] and security "guru."[7]

File:Smallbsdusage.gif
Pie chart showing the proportion of users of each BSD variant from a BSD usage survey. Each participant was permitted to indicate multiple BSD variants

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 in October of the same year by OpenBSD 2.0.[8] Since then, the project has followed a schedule of a release every six months, each of which is maintained and supported for one year. The latest release, OpenBSD 4.1, appeared[9] on May 1, 2007.

Just how widely OpenBSD is used is hard to ascertain: the developers do not collect and publish usage statistics and there are few other sources of information. The nascent BSD Certification project performed a usage survey which revealed that 32.8% of BSD users (1420 of 4330 respondents) were using OpenBSD,[10] placing it second of the four major BSD variants, behind FreeBSD with 77.0% and ahead of NetBSD with 16.3%.[11] The DistroWatch website, well-known in the Linux community and often used as a reference for popularity, publishes page hits for each of the Linux distributions and other operating systems it covers. As of April 14, 2007 it places OpenBSD in 55th place, with 121 hits per day. FreeBSD is in 16th place with 478 hits per day and a number of Linux distributions range between them.

Open source and open documentation

When OpenBSD was created, Theo de Raadt decided that the source should be available for anyone to read at any time, so, with the assistance of Chuck Cranor,[12] he set up a public, anonymous CVS server. This was the first of its kind in the software development world: at the time, the tradition was for only a small team of developers to have access to a project's source repository. This practice had downsides, notably that outside contributors had no way to closely follow a project's development and contributed work would often duplicate already completed efforts. This decision led to the name OpenBSD and signalled the project's insistence on open and public access to both source code and documentation.

A revealing incident regarding open documentation occurred in March 2005, when de Raadt posted a message[13] to the openbsd-misc mailing list. He announced that after four months of discussion, Adaptec had yet to disclose the required documentation to improve the OpenBSD drivers for its AAC RAID controllers. As in similar circumstances in the past, he encouraged the OpenBSD community to become involved and express their opinion to Adaptec. Shortly after this, FreeBSD committer, former Adaptec employee and author of the FreeBSD AAC RAID support Scott Long[14] castigated de Raadt[15] on the OSNews website for not contacting him directly regarding the issues with Adaptec. This caused the discussion to spill over onto the freebsd-questions mailing list, where the OpenBSD project leader countered[16] by claiming that he had received no previous offer of help from Scott Long nor been referred to him by Adaptec. The debate was amplified[17] by disagreements between members of the two camps regarding the use of binary blob drivers and non-disclosure agreements (NDAs): OpenBSD developers do not permit the inclusion of closed source binary drivers in the source tree and are reluctant to sign NDAs. However, the policy of the FreeBSD project has been less strict and much of the Adaptec RAID management code Scott Long proposed as assistance for OpenBSD was closed source or written under an NDA. As no documentation was forthcoming before the deadline for release of OpenBSD 3.7, support for Adaptec AAC RAID controllers was removed from the standard OpenBSD kernel.

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."[18] He went on to say that vendor binary drivers are unacceptable, as they cannot be trusted and there is "no way to fix [them] ... when they break," that even vendor source is only "marginally acceptable" and still difficult to fix when problems occur, and further commented "if we cannot maintain a driver after the vendor stops caring, we ... have a broken hardware [sic]."

Licensing

OpenBSD 3.7 running X.Org with the JWM window manager

A goal of the OpenBSD project is to "maintain the spirit of the original Berkeley Unix copyrights," which permitted a "relatively un-encumbered Unix source distribution."[19] To this end, the Internet Systems Consortium (ISC) licence, a simplified version of the BSD licence with wording removed that is unnecessary under the Berne convention, is preferred for new code, but the MIT or BSD licences are accepted. The widely used GNU General Public License is considered overly restrictive in comparison with these:[20] code licensed under it, and other licences the project sees as undesirable, is no longer accepted for addition to the base system. In addition, existing code under such licences is actively replaced or relicensed when possible, except in some cases, such as the GNU Compiler Collection (GCC), where there is no suitable replacement and creating one would be time-consuming and impractical. Despite this, OpenBSD has made some significant strides in this area: of particular note is the development of OpenSSH, based on the original SSH suite and developed further by the OpenBSD team. It first appeared in OpenBSD 2.6 and is now the single most popular SSH implementation, available as standard or as a package on many operating systems. Also worth mentioning is the development, after licence restrictions were imposed on IPFilter, of the pf packet filter, which first appeared[21] in OpenBSD 3.0 and is now available in DragonFly BSD, NetBSD and FreeBSD; more recently, OpenBSD releases have seen the GPL licensed tools bc, dc, diff, grep, gzip, nm, pkg-config, RCS, sendbug (part of GNATS) and size replaced with BSD licensed equivalents. OpenBSD developers are also behind OpenBGPD, OpenOSPFD, OpenNTPD and OpenCVS, BSD licensed alternatives to existing software.

In June 2001, triggered by concerns over Darren Reed's modification of IPFilter's licence wording, a systematic licence audit of the OpenBSD ports and source trees was undertaken.[22] 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 licence. To ensure that all licences 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, including the multicast routing tools, mrinfo and map-mbone,[23] which were licensed by Xerox for research only, were relicensed so that OpenBSD could continue to use them. Also of note during this audit was the removal of all software produced by Daniel J. Bernstein from the OpenBSD ports tree. 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.[24] The removal led to a clash with Bernstein who felt the removal of his software to be uncalled for and cited the Netscape web browser as much less free, accusing the OpenBSD developers of hypocrisy for permitting Netscape to remain while removing his software.[25] The OpenBSD project's stance was that Netscape, although not open source, had licence conditions that could be more easily met;[26] they asserted that Bernstein's demand for control of derivatives would lead to a great deal of additional work and that removal was the most appropriate way to comply with his requirements. At present, Daniel J. Bernstein's software is still absent from the ports tree.

Security and code auditing

Further information: OpenBSD security features

Shortly after OpenBSD's creation, Theo de Raadt was contacted by a local security software company named Secure Networks, Inc. or SNI.[27][28] They were developing a "network security auditing tool" called Ballista (later renamed to Cybercop Scanner after SNI was purchased by Network Associates) which was intended to find and attempt to exploit possible software security flaws. This coincided well with de Raadt's own interest in security, so the two agreed to cooperate, a relationship that was of particular use leading up to the release of OpenBSD 2.3[29] and helped to form the focal point of the project: OpenBSD developers would attempt to do what was right, proper or secure, even at the cost of ease, speed or functionality. As bugs within OpenBSD became harder to find and exploit, the security company found that it was too difficult, or not cost effective, to handle such obscure problems. After years of cooperation, the two parties decided that their goals together had been met and parted ways.

Until June 2002, the OpenBSD website featured the slogan:

No remote computer hole in the default install, in nearly 6 years.

In June 2002, Mark Dowd of Internet Security Systems disclosed a bug in the OpenSSH code implementing challenge-response authentication.[30] This vulnerability in the OpenBSD default installation allowed an attacker remote access to the root account, and was extremely serious, partly due to the widespread use of OpenSSH by that time: the bug affected a considerable number of other operating systems.[31] This problem necessitated the adjustment of the slogan on the OpenBSD website to:

Only one remote hole in the default install, in more than 10 years.

This was changed on March 13 2007 to read "two remote holes," after Core Security Technologies[32] disclosed a network-related remote vulnerability.[33]

This statement has been criticized because little is enabled in a default install of OpenBSD and releases have included software that was later found to have remote holes; 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. For example, OpenBSD's minimal defaults fit in with standard computer security practice of enabling as few services as possible on production machines, and the project uses open source and code auditing practices argued to be important elements of a security system.[34]

OpenBSD 3.8-current booting. 3.8 saw security changes to the malloc function

OpenBSD includes a large number of specific features designed to improve security, including API and toolchain alterations, such as the arc4random, issetugid, strlcat, strlcpy and strtonum functions and a static bounds checker; memory protection techniques to guard against invalid accesses, such as ProPolice, StackGhost, the W^X (W xor X) page protection features, as well as alterations to malloc; and cryptography and randomization features, including network stack enhancements and the addition of the Blowfish cipher for password encryption. To reduce the risk of a vulnerability or misconfiguration allowing privilege escalation, some 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.[35] Privilege revocation is similar and involves a program performing any necessary operations with the privileges it starts with then dropping them, and 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 features to OpenBSD versions of common applications, including tcpdump and the Apache web server, which, due to licensing issues with the later Apache 2 series, is a heavily patched 1.3.29 release.

The project has a policy of continually auditing code for security problems, work developer Marc Espie has described as "never finished ... more a question of process than of a specific bug being hunted."[36] 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." Along with DragonFly, OpenBSD is one of the two open source operating systems with a policy of seeking out examples of classic, K&R C code and converting it to the more modern ANSI equivalent—this involves no functional change and is purely for readability and consistency reasons. A standard code style, the Kernel Normal Form, which dictates how code must look in order to be easily maintained and understood, must be applied to all code before it is considered for inclusion in the base operating system; existing code is actively updated to meet the style requirements.

Uses

OpenBSD's security enhancements, built-in cryptography and the pf firewall suit it for use in the security industry, particularly for firewalls, intrusion-detection systems and VPN gateways. It is also commonly used for servers which must resist cracking and DoS attacks, and due to including the spamd daemon, it sometimes is used in mail filtering applications.

Several proprietary systems are based on OpenBSD, including Profense from Armorlogic ApS,[37] AccessEnforcer from Calyptix Security,[38] GeNUGate and GeNUBox from GeNUA mbH,[39] RTMX O/S from RTMX Inc,[40] syswall from Syscall Network Solutions AG,[41] HIOBMessenger from topX, and various security appliances made by .vantronix GmbH.[42] Of these, both GeNUA and RTMX have contributed back to OpenBSD: GeNUA funded the development of SMP on the i386 platform and RTMX have sent patches to add further POSIX compliance to the system. Several open source operating systems have also been derived from OpenBSD, notably Anonym.OS and MirOS BSD, as well as the now defunct ekkoBSD, MicroBSD and Gentoo/OpenBSD. In addition, code from many of the OpenBSD system tools has been used in recent versions of Microsoft's Services for UNIX, an extension to the Windows operating system which provides some Unix-like functionality, originally based on 4.4BSD-Lite. Core force, a security product for Windows, is based on OpenBSD's pf firewall. There have also been projects which use OpenBSD as part of images for embedded systems, including OpenSoekris and flashdist; together with tools like nsh, these allow Cisco-like embedded devices to be created.[43]

OpenBSD 3.8 running X.Org with the default FVWM 2.2.5 window manager

OpenBSD ships with the X window system. Following the XFree86 licence change, it includes a recent X.Org release; an older XFree86 3.3 release is also available for legacy video cards. With these, it is possible to use OpenBSD as a desktop or workstation, making use of a desktop environment, window manager or both to give the X desktop a wide range of appearances. The OpenBSD ports tree contains many of the most popular tools for desktop use, including desktop environments GNOME, KDE, and Xfce; web browsers Konqueror, Mozilla Firefox and Opera; and multimedia programs MPlayer, VLC media player and xine. In addition, graphical software for many uses is available from both the ports tree and by compiling POSIX compliant software. Also available are compatibility layers, which allow binary code compiled for other operating systems, including Linux, FreeBSD, SunOS and HP-UX, to be run. However, since hardware providers such as video card manufacturers ATI and NVIDIA refuse to release open source drivers or documentation for the 3D capabilities of their hardware, OpenBSD lacks accelerated 3D graphics support.

OpenBSD's performance and usability is occasionally criticised. Felix von Leitner's performance and scalability tests,[44] indicated that OpenBSD lagged behind other operating systems. In response, OpenBSD users and developers criticised von Leitner's objectivity and methodology, and asserted that although performance is given consideration, security and correct design are prioritised, with developer Nick Holland commenting: "It all boils down to what you consider important."[45] OpenBSD is also a relatively small project, particularly when compared with FreeBSD and Linux, and developer time is sometimes seen as better spent on security enhancements than performance optimisations. Critics of usability often point out the lack of user-friendly configuration tools, the bare default installation,[46] and "spartan" and "intimidating" installer.[47] These see much the same rebuttals as performance: a preference for simplicity, reliability and security; as one reviewer admits, "running an ultra-secure operating system can be a bit of work."[48]

Distribution and marketing

OpenBSD is available freely in various ways: the source can be retrieved by anonymous CVS or CVSup, and binary releases and development snapshots can be downloaded either by FTP or HTTP. Prepackaged CD-ROM sets 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 its artwork and other bonuses, are one of the project's few sources of income, funding hardware, bandwidth and other expenses. To encourage the sale of the official CD-ROMs, OpenBSD makes only a small install ISO image available for download rather than providing full release images.

In common with several other operating systems, OpenBSD uses ports and packages systems to allow for easy installation and management of programs which are not part of the base operating system. Originally based on the FreeBSD ports tree, the system is now quite distinct. Additionally, major changes have been made since the 3.6 release, including the replacement of the package tools, the tools available to the user to manipulate packages, by more capable versions, written in Perl by Marc Espie. In contrast to FreeBSD, the OpenBSD ports system is intended as a source used to create the end product, the packages: installing a port first creates a package and then installs it using the package tools. Packages are built in bulk by the OpenBSD team and provided for download with each release. OpenBSD is also unique among the BSDs in that 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, 3.7 are not suitable for use with 3.6 and vice versa, a policy which lends a great deal of stability to the development process, but means that the software in ports for the latest OpenBSD release can lag somewhat from the latest version available from the author.

File:Paintedpuffy1000X907px.gif
Puffy, painted

Around the time of the OpenBSD 2.7 release, the original mascot, a BSD daemon with a trident and aureola, was replaced by Puffy, traditionally said to be a pufferfish. In fact pufferfish do not possess spikes and images of Puffy are closer to a similar species, the porcupinefish. Puffy was selected because of the Blowfish encryption algorithm used in OpenSSH and the strongly defensive image of the porcupinefish with its spikes to deter predators. He quickly became very popular, mainly because of the appealing image of the fish and his distinction from the BSD daemon, also used by FreeBSD, and the horde of daemons then used by NetBSD. Puffy made his first public appearance in OpenBSD 2.6 and, since then, has appeared in a number of guises on tee-shirts and posters. These have included Puffiana Jones, the famed hackologist and adventurer, seeking out the Lost RAID; Puffathy, a little Alberta girl, who must work with Taiwan to save the day; Sir Puffy of Ramsay, a freedom fighter who, with Little Bob of Beckley, took from the rich and gave to all; and Puff Daddy, famed rapper and political icon.

After a number of releases, OpenBSD has become notorious for its catchy songs and interesting and often comical artwork. The promotional material of early OpenBSD releases did not have a cohesive theme or design but, starting with OpenBSD 3.0, 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. At first they were done lightly and only intended to add humour but, as the concept has evolved, they have become a part of OpenBSD advocacy, with each release expanding a moral or political point important to the project, often through parody. Past themes have included: in OpenBSD 3.8, the Hackers of the Lost RAID, a parody of Indiana Jones linked to the new RAID tools featured as part of the release; The Wizard of OS, making its debut in OpenBSD 3.7, based on the work of Pink Floyd and a parody of The Wizard of Oz related to the project's recent wireless work; and OpenBSD 3.3's Puff the Barbarian, including an 80s rock-style song and parody of Conan the Barbarian, alluding to open documentation.

In addition to the slogans used on tee-shirts and posters for releases, the project occasionally produces other material: over the years, catchphrases have included "Sending script kiddies to /dev/null since 1995," "Functional, secure, free - choose 3," "Secure by default," and a few insider slogans, only available on tee-shirts made for developer gatherings, such as "World class security for much less than the price of a cruise missile" and a crufty old octopus proclaiming "Shut up and hack!"

Books

A number of books on OpenBSD have been published, including:

See also

Notes and references

  1. ^ List of supported platforms on the OpenBSD website.
  2. ^ Glass, Adam. Message to netbsd-users: Theo De Raadt(sic), December 23, 1994. Visited January 8, 2006.
  3. ^ Wayner, Peter. Free For All: How Linux and the Free Software Movement Undercut the High Tech Titans, 18.3 Flames, Fights, and the Birth of OpenBSD, 2000. Visited January 6, 2006.
  4. ^ Forbes. Is Linux For Losers? June 16, 2005. Visited January 8, 2006.
  5. ^ NewsForge. Theo de Raadt gives it all to OpenBSD, January 30, 2001. Visited January 8, 2006.
  6. ^ In this message the NetBSD core team acknowledge de Raadt's "positive contributions" to the project despite its problems with him.
  7. ^ Tux Journal. A good morning with: Theo de Raadt, June 2, 2005. Visited April 21, 2006
  8. ^ de Raadt, Theo. Mail to openbsd-announce: The OpenBSD 2.0 release, October 18, 1996. Visited December 10, 2005.
  9. ^ Beck, Bob. Mail to announce@openbsd.org: OpenBSD 4.1 Released. Visited May 2, 2006.
  10. ^ The BSD Certification Group.; PDF of usage survey results.
  11. ^ Multiple selections were permitted as a user may use multiple BSD variants side by side.
  12. ^ Chuck Cranor's site.
  13. ^ de Raadt, Theo. Mail to openbsd-misc: Adaptec AAC raid support, March 18, 2005. Visited December 9, 2005.
  14. ^ Scott Long's site.
  15. ^ Long, Scott. Post to OSNews: From a BSD and former Adaptec person..., March 19, 2005. Visited December 9, 2005.
  16. ^ de Raadt, Theo. Mail to freebsd-questions: aac support, March 19, 2005. Visited December 9, 2005.
  17. ^ de Raadt, Theo. Mail to freebsd-questions: aac support, March 19, 2005. Visited December 9, 2005.
  18. ^ de Raadt, Theo. Presentation at OpenCON, December 2006. Visited December 7, 2006.
  19. ^ OpenBSD.org. Copyright Policy. Visited January 7, 2006.
  20. ^ NewsForge. BSD cognoscenti on Linux, June 15, 2005. Visited January 7, 2006.
  21. ^ Hartmeier, Daniel. Design and Performance of the OpenBSD Stateful Packet Filter (pf). Visited December 9, 2005.
  22. ^ NewsForge. OpenBSD and ipfilter still fighting over license disagreement, June 06, 2001. Visited November 23, 2005.
  23. ^ Man pages: mrinfo and map-mbone.
  24. ^ de Raadt, Theo. Mail to openbsd-misc: Re: Why were all DJB's ports removed? No more qmail?, August 24, 2001. Visited December 9, 2005.
  25. ^ Bernstein, DJ. Mail to openbsd-misc: Re: Why were all DJB's ports removed? No more qmail?, August 27, 2001. Visited December 9, 2005.
  26. ^ Espie, Marc. Mail to openbsd-misc: Re: Why were all DJB's ports removed? No more qmail?, August 28, 2001. Visited December 9, 2005.
  27. ^ The Age. Staying on the cutting edge, October 8, 2004. Visited January 8, 2006.
  28. ^ ONLamp.com. Interview with OpenBSD developers: The Essence of OpenBSD, July 17, 2003. Visited December 18, 2005.
  29. ^ Theo de Raadt on SNI: "Without their support at the right time, this release probably would not have happened." From the 2.3 release announcement. Visited December 19, 2005.
  30. ^ Internet Security Systems. OpenSSH Remote Challenge Vulnerability, June 26, 2002. Visited December 17, 2005.
  31. ^ A partial list of affected operating systems.
  32. ^ Core Security Technologies' homepage.
  33. ^ Core Security Technologies. Mail to bugtraq: OpenBSD's IPv6 mbufs remote kernel buffer overflow. March 13, 2007. Visited March 13, 2007.
  34. ^ Wheeler, David A. Secure Programming for Linux and Unix HOWTO, 2.4. Is Open Source Good for Security?, March 3, 2003. Visited December 10, 2005.
  35. ^ Provos, Niels. Privilege Separated OpenSSH. Visited January 30, 2006.
  36. ^ O'Reilly Network. An Interview with OpenBSD's Marc Espie, March 18, 2004. Visited January 24, 2006.
  37. ^ Armorlogic ApS's homepage.
  38. ^ Calyptix Security's website.
  39. ^ GeNUA mbH's homepage.
  40. ^ RTMX Inc homepage.
  41. ^ Syscall Network Solutions AG's site.
  42. ^ .vantronix GmbH's homepage.
  43. ^ OpenSoekris, flashdist and nsh.
  44. ^ Scalability test results and conclusions.
  45. ^ Holland, Nick. Mail to openbsd-misc: Re: OpenBSD Benchmarked... results: poor!, October 19, 2003. Visited January 8, 2006.
  46. ^ NewsForge. Trying out the new OpenBSD 3.8, November 2, 2005. Visited January 8, 2006.
  47. ^ NewsForge. Review: OpenBSD 3.5, July 22, 2004. Visited January 8, 2006.
  48. ^ DistroWatch. OpenBSD - For Your Eyes Only, 2004. Visited January 8, 2006.

External links

Wikimedia Commons has media related to OpenBSD.
Retrieved from "https://en.wikipedia.org/w/index.php?title=OpenBSD&oldid=130432366"