Annotation of www/security.html, Revision 1.32
1.1 deraadt 1: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML Strict//EN">
2: <html>
3: <head>
1.20 deraadt 4: <title>OpenBSD Security</title>
1.1 deraadt 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.22 deraadt 19:
1.14 deraadt 20: OpenBSD believes in strong security. Our aspiration is to be NUMBER
1.22 deraadt 21: ONE in the industry for security (if we are not already there). Our
22: open software development model permits us to take a more
23: uncompromising view towards increased security than Sun, SGI, IBM, HP,
24: or other vendors are able to. We can make changes the vendors would
1.27 deraadt 25: not make. Also, since OpenBSD is exported with <a href=crypto.html>
1.28 deraadt 26: cryptography software, we are able to take cryptographic
27: approaches towards fixing security problems.</a><p>
1.18 deraadt 28:
29: Like most readers of the
1.13 deraadt 30: <a href=http://www.geek-girl.com/bugtraq/index.html>
1.18 deraadt 31: BUGTRAQ mailing list</a>,
32: we believe in full disclosure of security problems. We believe that
33: security information moves very fast in crackers circles. Our
34: experience shows that coding and release of proper security fixes
35: typically requires about an hour of work resulting in very fast fix
36: turnaround. Thus we think that full disclosure helps the people who
1.22 deraadt 37: really care about security.<p>
1.15 deraadt 38:
1.12 deraadt 39: Our security auditing team typically has between six and twelve
1.15 deraadt 40: members, and most of us continually search for and fix new security
41: holes. We have been auditing since the summer of 1997. The process we
1.12 deraadt 42: followed to increase security was simply a comprehensive file-by-file
43: analysis of every critical software component. Flaws were found in
44: just about every area of the system. Entire new classes of security
45: problems were found while we were doing the audit, and in many cases
46: source code which had been audited earlier had to be re-audited with
1.22 deraadt 47: these new flaws in mind.<p>
1.12 deraadt 48:
1.31 deraadt 49: Some members of our security auditing team work for
50: <a href=http://www.secnet.com>Secure Networks</a>, the company that
1.32 ! deraadt 51: makes the industry's premier network security scanning software
! 52: package Ballista.
1.31 deraadt 53: This company does a lot of security research, and this fits in well
54: with the OpenBSD stance.<p>
55:
1.16 deraadt 56: Another facet of our security auditing process is it's proactiveness.
57: In almost all cases we have found that the determination of
58: exploitability is not an issue. During our auditing process we find
59: many bugs, and endeavor to simply fix them even though exploitability
60: is not proven. We have fixed many simple and obvious careless
61: programming errors in code and then only months later discovered that
1.29 deraadt 62: the problems were in fact exploitable. In other cases we have been
63: saved from full exploitability of complex step-by-step attacks because
64: we had fixed one of the steps. An example of where we did this is the
1.30 deraadt 65: <a href=http://www.secnet.com/sni-advisories/sni-19.bsd.lpd.advisory.html>
1.29 deraadt 66: lpd advisory from
67: Secure Networks.</a><p>
68:
69: This proactive auditing
1.16 deraadt 70: process has really paid off. Statements like ``This problem was fixed
71: in OpenBSD about 6 months ago'' have become commonplace in security
1.28 deraadt 72: forums like <a href=http://www.geek-girl.com/bugtraq/index.html>BUGTRAQ</a>.<p>
1.15 deraadt 73:
1.14 deraadt 74: The auditing process is not over yet, and as you can see we continue
1.28 deraadt 75: to find and fix new security flaws.<p>
1.12 deraadt 76:
77: <p>
78: <h3><font color=#e00000><strong>OpenBSD 2.1 Security Advisories</strong></font></h3>
1.11 deraadt 79: These are the OpenBSD 2.1 advisories. All these problems are solved
80: in OpenBSD 2.2. Some of these problems still exist in other
1.1 deraadt 81: operating systems.
82:
83: <ul>
1.27 deraadt 84: <li><a href=advisories/rfork>Rfork() system call flaw (patch included)</a>
85: <li><a href=advisories/procfs>Procfs flaws (patch included)</a>
86: <li><a href=advisories/signals>Deviant Signals (patch included)</a>
1.9 deraadt 87: </ul>
88:
89: <p>
1.12 deraadt 90: <h3><font color=#e00000><strong>OpenBSD 2.2 Security Advisories</strong></font></h3>
1.11 deraadt 91: These are the OpenBSD 2.2 advisories. All these problems are
1.9 deraadt 92: solved in OpenBSD current. Some of these problems still exist in other
1.14 deraadt 93: operating systems.
1.9 deraadt 94:
95: <ul>
1.27 deraadt 96: <li><a href=errata.html#f00f>Intel P5 f00f lockup (patch included)</a>
97: <li><a href=errata.html#sourceroute>
1.11 deraadt 98: Sourcerouted Packet Acceptance (patch included)</a>
1.27 deraadt 99: <li><a href=errata.html#ruserok>Setuid coredump & Ruserok() flaw (patch included)</a>
100: <li><a href=errata.html#mmap>Read-write mmap() flaw (patch included)</a>
1.1 deraadt 101: </ul>
102:
1.21 deraadt 103:
104: <p>
105: <h3><font color=#e00000><strong>Watching our Security Changes</strong></font></h3>
106: Since we take a proactive stance with security, we are continually
107: finding and fixing new security problems. Not all of these problems
108: get widely reported because (as stated earlier) many of them are not
109: confirmed to be exploitable. We do not have the time resources to
110: make these changes available in the above format.<p>
111:
112: Thus there are usually minor security fixes in the current source code
113: beyond the previous major OpenBSD release. We make a limited
114: gaurantee that these problems are of limited impact and unproven
115: exploitability. If we discover a problem definately matters for
116: security, patches will show up here quickly.<p>
117:
118: People who are really concerned with critical
119: security can do a number of things:<p>
120:
121: <ul>
122: <li>If you understand security issues, watch our
1.27 deraadt 123: <a href=mail.html>source-changes mailing list</a> and keep an
1.23 deraadt 124: eye out for things which appear security related. Since
1.21 deraadt 125: exploitability is not proven for many of the fixes we make,
126: do not expect the relevant commit message to say "SECURITY FIX!".
127: If a problem is proven and serious, a patch will be available
128: here very shortly after.
129: <li>Track our current source code tree, and teach yourself how to do a
1.29 deraadt 130: complete system build from time to time (read /usr/src/Makefile
131: carefully). Users can make the assumption that the current
132: source tree always has stronger security than the previous release.
133: <li>Install a binary <a href=snapshots.html>snapshot</a> for your
134: architecure, which are made available fairly often. For
135: instance, an i386 snapshot is typically made available weekly.
1.21 deraadt 136: </ul>
137:
1.9 deraadt 138: <p>
1.12 deraadt 139: <h3><font color=#e00000><strong>Other Resources</strong></font></h3>
1.3 deraadt 140: Other security advisories that have (in the past) affected OpenBSD can
1.4 deraadt 141: be found at the <a href=http://www.secnet.com/nav1.html>Secure Networks archive</a>.
1.25 deraadt 142: Some OpenBSD audit team members worked with Secure Networks on discovering
143: and solving the problems detailed in some of their security advisories.
1.3 deraadt 144:
1.5 deraadt 145: <p> If you find a new security problem, you can mail it to
1.6 deraadt 146: <a href=mailto:deraadt@openbsd.org>deraadt@openbsd.org</a>.
1.7 deraadt 147: <br>
1.5 deraadt 148: If you wish to PGP encode it (but please only do so if privacy is very
1.27 deraadt 149: urgent, since it is inconvenient) use this <a href=advisories/pgpkey>pgp key</a>.
1.5 deraadt 150:
1.2 deraadt 151: <hr>
1.27 deraadt 152: <a href=index.html><img src=/back.gif border=0 alt=OpenBSD></a>
1.24 deraadt 153: <a href=mailto:www@openbsd.org>www@openbsd.org</a>
154: <br>
1.32 ! deraadt 155: <small>$OpenBSD: security.html,v 1.31 1998/02/24 01:03:14 deraadt Exp $</small>
1.1 deraadt 156:
1.24 deraadt 157: </body>
158: </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