Annotation of www/security.html, Revision 1.16
1.1 deraadt 1: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML Strict//EN">
2: <html>
3: <head>
4: <title>OpenBSD</title>
5: <link rev=made href=mailto:www@openbsd.org>
6: <meta name="resource-type" content="document">
7: <meta name="description" content="OpenBSD advisories">
8: <meta name="keywords" content="openbsd,main">
9: <meta name="distribution" content="global">
10: <meta name="copyright" content="This document copyright 1997 by OpenBSD.">
11: </head>
12:
13: <BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#23238E">
14:
1.2 deraadt 15: <img alt="[OpenBSD]" SRC="/images/smalltitle.gif">
1.1 deraadt 16:
1.2 deraadt 17: <p>
1.12 deraadt 18: <h3><font color=#e00000><strong>OpenBSD Security Views</strong></font></h3>
1.14 deraadt 19: OpenBSD believes in strong security. Our aspiration is to be NUMBER
20: ONE in the industry for security. Due to our open software
21: development model, we are able to take a more uncompromising view
22: towards increasing security than Sun, SGI, IBM, HP, or other vendors
23: are able to.
1.12 deraadt 24:
25: <p>
1.13 deraadt 26: Like most members of the
27: <a href=http://www.geek-girl.com/bugtraq/index.html>
28: BUGTRAQ mailing list (which rarely sees OpenBSD security reports
29: these days :-)</a>,
30: we believe in full disclosure of security problems. We have found
31: that the coding of proper fixes to security problems typically only
32: requires about 4-5 minutes of coding. Thus we typically have fixes
33: available extremely quickly.
34:
35: <p>
1.15 deraadt 36:
1.12 deraadt 37: Our security auditing team typically has between six and twelve
1.15 deraadt 38: members, and most of us continually search for and fix new security
39: holes. We have been auditing since the summer of 1997. The process we
1.12 deraadt 40: followed to increase security was simply a comprehensive file-by-file
41: analysis of every critical software component. Flaws were found in
42: just about every area of the system. Entire new classes of security
43: problems were found while we were doing the audit, and in many cases
44: source code which had been audited earlier had to be re-audited with
45: these new flaws in mind.
46:
47: <p>
1.16 ! deraadt 48: Another facet of our security auditing process is it's proactiveness.
! 49: In almost all cases we have found that the determination of
! 50: exploitability is not an issue. During our auditing process we find
! 51: many bugs, and endeavor to simply fix them even though exploitability
! 52: is not proven. We have fixed many simple and obvious careless
! 53: programming errors in code and then only months later discovered that
! 54: the problems were in fact exploitable. This proactive auditing
! 55: process has really paid off. Statements like ``This problem was fixed
! 56: in OpenBSD about 6 months ago'' have become commonplace in security
! 57: forums like BUGTRAQ.
1.15 deraadt 58:
59: <p>
1.14 deraadt 60: The auditing process is not over yet, and as you can see we continue
61: to find and fix new security flaws.
1.12 deraadt 62:
63: <p>
64: <h3><font color=#e00000><strong>OpenBSD 2.1 Security Advisories</strong></font></h3>
1.11 deraadt 65: These are the OpenBSD 2.1 advisories. All these problems are solved
66: in OpenBSD 2.2. Some of these problems still exist in other
1.1 deraadt 67: operating systems.
68:
69: <ul>
1.11 deraadt 70: <li><a href=rfork>Rfork() system call flaw (patch included)</a>
71: <li><a href=procfs>Procfs flaws (patch included)</a>
72: <li><a href=signals>Deviant Signals (patch included)</a>
1.9 deraadt 73: </ul>
74:
75: <p>
1.12 deraadt 76: <h3><font color=#e00000><strong>OpenBSD 2.2 Security Advisories</strong></font></h3>
1.11 deraadt 77: These are the OpenBSD 2.2 advisories. All these problems are
1.9 deraadt 78: solved in OpenBSD current. Some of these problems still exist in other
1.14 deraadt 79: operating systems.
1.9 deraadt 80:
81: <ul>
1.11 deraadt 82: <li><a href=/errata.html#f00f>Intel P5 f00f lockup (patch included)</a>
83: <li><a href=/errata.html#sourceroute>
84: Sourcerouted Packet Acceptance (patch included)</a>
85: <li><a href=/errata.html#ruserok>Setuid coredump & Ruserok() flaw (patch included)</a>
86: <li><a href=/errata.html#mmap>Read-write mmap() flaw (patch included)</a>
1.1 deraadt 87: </ul>
88:
1.9 deraadt 89: <p>
1.12 deraadt 90: <h3><font color=#e00000><strong>Other Resources</strong></font></h3>
1.3 deraadt 91: Other security advisories that have (in the past) affected OpenBSD can
1.4 deraadt 92: be found at the <a href=http://www.secnet.com/nav1.html>Secure Networks archive</a>.
1.3 deraadt 93:
1.5 deraadt 94: <p> If you find a new security problem, you can mail it to
1.6 deraadt 95: <a href=mailto:deraadt@openbsd.org>deraadt@openbsd.org</a>.
1.7 deraadt 96: <br>
1.5 deraadt 97: If you wish to PGP encode it (but please only do so if privacy is very
98: urgent, since it is inconvenient) use this <a href=pgpkey>pgp key</a>.
99:
1.2 deraadt 100: <hr>
1.1 deraadt 101: <font size="-1">
1.2 deraadt 102: <em>This site Copyright © 1996, 1997 OpenBSD.</em><br>
1.16 ! deraadt 103: $OpenBSD: index.html,v 1.15 1998/02/19 22:37:51 deraadt Exp $
1.1 deraadt 104: </font>
105:
106: </BODY>
107: </HTML>
![[BACK]](/icons/back.gif){kind=icon}
Return to security.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www