Annotation of www/security.html, Revision 1.424
1.294 david 1: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
2: "http://www.w3.org/TR/html4/loose.dtd">
1.1 deraadt 3: <html>
4: <head>
1.20 deraadt 5: <title>OpenBSD Security</title>
1.345 tom 6: <link rel="alternate" type="application/rss+xml" title="OpenBSD errata (external)" href="http://www.undeadly.org/cgi?action=errata">
1.294 david 7: <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
1.1 deraadt 8: <meta name="description" content="OpenBSD advisories">
1.403 sthen 9: <meta name="copyright" content="This document copyright 1997-2014 by OpenBSD.">
1.421 sthen 10: <link rel="canonical" href="http://www.openbsd.org/security.html">
1.1 deraadt 11: </head>
12:
1.274 david 13: <body bgcolor="#ffffff" text="#000000" link="#23238E">
1.210 jsyn 14: <a href="index.html"><img alt="[OpenBSD]" height="30" width="141" src="images/smalltitle.gif" border="0"></a>
1.106 deraadt 15: <p>
1.294 david 16: <h2><font color="#e00000">Security</font></h2>
17: <hr>
1.1 deraadt 18:
1.406 deraadt 19: For security advisories for specific releases, click below:
1.294 david 20: <p>
1.406 deraadt 21:
1.418 tedu 22: <a href="errata21.html">2.1</a>,
23: <a href="errata22.html">2.2</a>,
24: <a href="errata23.html">2.3</a>,
25: <a href="errata24.html">2.4</a>,
26: <a href="errata25.html">2.5</a>,
27: <a href="errata26.html">2.6</a>,
28: <a href="errata27.html">2.7</a>,
29: <a href="errata28.html">2.8</a>,
30: <a href="errata29.html">2.9</a>,
31: <a href="errata30.html">3.0</a>,
32: <a href="errata31.html">3.1</a>,
33: <a href="errata32.html">3.2</a>,
34: <a href="errata33.html">3.3</a>,
35: <a href="errata34.html">3.4</a>,
36: <a href="errata35.html">3.5</a>,
37: <a href="errata36.html">3.6</a>,
1.420 schwarze 38: <a href="errata37.html">3.7</a>,
1.365 deraadt 39: <br>
1.418 tedu 40: <a href="errata38.html">3.8</a>,
41: <a href="errata39.html">3.9</a>,
42: <a href="errata40.html">4.0</a>,
43: <a href="errata41.html">4.1</a>,
44: <a href="errata42.html">4.2</a>,
45: <a href="errata43.html">4.3</a>,
46: <a href="errata44.html">4.4</a>,
47: <a href="errata45.html">4.5</a>,
48: <a href="errata46.html">4.6</a>,
49: <a href="errata47.html">4.7</a>,
50: <a href="errata48.html">4.8</a>,
51: <a href="errata49.html">4.9</a>,
52: <a href="errata50.html">5.0</a>,
53: <a href="errata51.html">5.1</a>,
54: <a href="errata52.html">5.2</a>,
55: <a href="errata53.html">5.3</a>,
1.420 schwarze 56: <a href="errata54.html">5.4</a>,
1.406 deraadt 57: <br>
1.419 jsg 58: <a href="errata55.html">5.5</a>,
1.420 schwarze 59: <a href="errata56.html">5.6</a>,
1.423 benno 60: <a href="errata57.html">5.7</a>,
61: <a href="errata58.html">5.8</a>.
1.406 deraadt 62: <br>
1.56 deraadt 63: <hr>
64:
1.294 david 65: <a name="goals"></a>
1.278 deraadt 66: <ul>
1.406 deraadt 67: <li><h3><font color="#e00000">Goals</font></h3><p>
1.22 deraadt 68:
1.14 deraadt 69: OpenBSD believes in strong security. Our aspiration is to be NUMBER
1.22 deraadt 70: ONE in the industry for security (if we are not already there). Our
71: open software development model permits us to take a more
1.424 ! tb 72: uncompromising view towards increased security than most vendors are
! 73: able to. We can make changes the vendors would
1.27 deraadt 74: not make. Also, since OpenBSD is exported with <a href=crypto.html>
1.45 deraadt 75: cryptography</a>, we are able to take cryptographic approaches towards
76: fixing security problems.<p>
1.18 deraadt 77:
1.288 matthieu 78: <a name="disclosure"></a>
1.294 david 79: <li><h3><font color="#e00000">Full Disclosure</font></h3><p>
1.106 deraadt 80:
1.45 deraadt 81: Like many readers of the
1.196 jufi 82: <a href="http://online.securityfocus.com/archive/1">
1.18 deraadt 83: BUGTRAQ mailing list</a>,
1.106 deraadt 84: we believe in full disclosure of security problems. In the
85: operating system arena, we were probably the first to embrace
86: the concept. Many vendors, even of free software, still try
87: to hide issues from their users.<p>
88:
89: Security information moves very fast in cracker circles. On the other
90: hand, our experience is that coding and releasing of proper security
91: fixes typically requires about an hour of work -- very fast fix
92: turnaround is possible. Thus we think that full disclosure helps the
93: people who really care about security.<p>
94:
1.288 matthieu 95: <a name="process"></a>
1.294 david 96: <li><h3><font color="#e00000">Audit Process</font></h3><p>
1.15 deraadt 97:
1.12 deraadt 98: Our security auditing team typically has between six and twelve
1.45 deraadt 99: members who continue to search for and fix new security holes. We
100: have been auditing since the summer of 1996. The process we follow to
101: increase security is simply a comprehensive file-by-file analysis of
1.106 deraadt 102: every critical software component. We are not so much looking for
103: security holes, as we are looking for basic software bugs, and if
1.138 deraadt 104: years later someone discovers the problem used to be a security
1.106 deraadt 105: issue, and we fixed it because it was just a bug, well, all the
106: better. Flaws have been found in just about every area of the system.
107: Entire new classes of security problems have been found during our
108: audit, and often source code which had been audited earlier needs
109: re-auditing with these new flaws in mind. Code often gets audited
110: multiple times, and by multiple people with different auditing
111: skills.<p>
1.12 deraadt 112:
1.94 deraadt 113: Some members of our security auditing team worked for Secure Networks,
114: the company that made the industry's premier network security scanning
115: software package Ballista (Secure Networks got purchased by Network
116: Associates, Ballista got renamed to Cybercop Scanner, and well...)
117: That company did a lot of security research, and thus fit in well
1.106 deraadt 118: with the OpenBSD stance. OpenBSD passed Ballista's tests with flying
119: colours since day 1.<p>
1.31 deraadt 120:
1.34 deraadt 121: Another facet of our security auditing process is its proactiveness.
1.45 deraadt 122: In most cases we have found that the determination of exploitability
123: is not an issue. During our ongoing auditing process we find many
124: bugs, and endeavor to fix them even though exploitability is not
125: proven. We fix the bug, and we move on to find other bugs to fix. We
126: have fixed many simple and obvious careless programming errors in code
127: and only months later discovered that the problems were in fact
128: exploitable. (Or, more likely someone on
1.197 jufi 129: <a href="http://online.securityfocus.com/archive/1">BUGTRAQ</a>
1.45 deraadt 130: would report that other operating systems were vulnerable to a `newly
131: discovered problem', and then it would be discovered that OpenBSD had
132: been fixed in a previous release). In other cases we have been saved
133: from full exploitability of complex step-by-step attacks because we
134: had fixed one of the intermediate steps. An example of where we
1.94 deraadt 135: managed such a success is the lpd advisory that Secure Networks put out.
136: <p>
1.29 deraadt 137:
1.288 matthieu 138: <a name="newtech"></a>
1.294 david 139: <li><h3><font color="#e00000">New Technologies</font></h3><p>
1.278 deraadt 140:
141: As we audit source code, we often invent new ways of solving problems.
142: Sometimes these ideas have been used before in some random application
143: written somewhere, but perhaps not taken to the degree that we do.
144: <p>
145:
146: <ul>
147: <li>strlcpy() and strlcat()
148: <li>Memory protection purify
149: <ul>
150: <li>W^X
151: <li>.rodata segment
152: <li>Guard pages
153: <li>Randomized malloc()
154: <li>Randomized mmap()
155: <li>atexit() and stdio protection
156: </ul>
1.295 otto 157: <li>Privilege separation
1.278 deraadt 158: <li>Privilege revocation
159: <li>Chroot jailing
160: <li>New uids
161: <li>ProPolice
1.424 ! tb 162: <li>... <a href="/innovations.html">and others</a>
1.278 deraadt 163: </ul>
164: <p>
165:
1.294 david 166: <li><h3><font color="#e00000">The Reward</font></h3><p>
1.106 deraadt 167:
1.45 deraadt 168: Our proactive auditing process has really paid off. Statements like
1.35 deraadt 169: ``This problem was fixed in OpenBSD about 6 months ago'' have become
1.45 deraadt 170: commonplace in security forums like
1.197 jufi 171: <a href="http://online.securityfocus.com/archive/1">BUGTRAQ</a>.<p>
1.35 deraadt 172:
1.45 deraadt 173: The most intense part of our security auditing happened immediately
1.80 espie 174: before the OpenBSD 2.0 release and during the 2.0->2.1 transition,
1.45 deraadt 175: over the last third of 1996 and first half of 1997. Thousands (yes,
176: thousands) of security issues were fixed rapidly over this year-long
177: period; bugs like the standard buffer overflows, protocol
178: implementation weaknesses, information gathering, and filesystem
179: races. Hence most of the security problems that we encountered were
180: fixed before our 2.1 release, and then a far smaller number needed
181: fixing for our 2.2 release. We do not find as many problems anymore,
182: it is simply a case of diminishing returns. Recently the security
183: problems we find and fix tend to be significantly more obscure or
184: complicated. Still we will persist for a number of reasons:<p>
1.36 deraadt 185:
1.35 deraadt 186: <ul>
1.45 deraadt 187: <li>Occasionally we find a simple problem we missed earlier. Doh!
1.35 deraadt 188: <li>Security is like an arms race; the best attackers will continue
1.45 deraadt 189: to search for more complicated exploits, so we will too.
190: <li>Finding and fixing subtle flaws in complicated software is
191: a lot of fun.
1.35 deraadt 192: </ul>
1.106 deraadt 193: <p>
1.15 deraadt 194:
1.14 deraadt 195: The auditing process is not over yet, and as you can see we continue
1.28 deraadt 196: to find and fix new security flaws.<p>
1.12 deraadt 197:
1.288 matthieu 198: <a name="default"></a>
1.294 david 199: <li><h3><font color="#e00000">"Secure by Default"</font></h3><p>
1.106 deraadt 200:
201: To ensure that novice users of OpenBSD do not need to become security
202: experts overnight (a viewpoint which other vendors seem to have), we
203: ship the operating system in a Secure by Default mode. All non-essential
204: services are disabled. As the user/administrator becomes more familiar
205: with the system, he will discover that he has to enable daemons and other
206: parts of the system. During the process of learning how to enable a new
207: service, the novice is more likely to learn of security considerations.<p>
208:
209: This is in stark contrast to the increasing number of systems that
210: ship with NFS, mountd, web servers, and various other services enabled
211: by default, creating instantaneous security problems for their users
212: within minutes after their first install.<p>
213:
1.288 matthieu 214: <a name="crypto"></a>
1.294 david 215: <li><h3><font color="#e00000">Cryptography</font></h3><p>
1.106 deraadt 216:
217: And of course, since the OpenBSD project is based in Canada, it is possible
218: for us to integrate cryptography. For more information, read the page
1.116 deraadt 219: outlining <a href=crypto.html>what we have done with cryptography</a>.</p>
1.106 deraadt 220:
1.294 david 221: <li><h3><font color="#e00000">Advisories</font></h3><p>
1.106 deraadt 222:
1.418 tedu 223: Please refer to the links at the top of this page.
1.106 deraadt 224:
1.288 matthieu 225: <a name="watching"></a>
1.294 david 226: <li><h3><font color="#e00000">Watching our Changes</font></h3><p>
1.106 deraadt 227:
1.21 deraadt 228: Since we take a proactive stance with security, we are continually
229: finding and fixing new security problems. Not all of these problems
1.80 espie 230: get widely reported because (as stated earlier) many of them are not
1.45 deraadt 231: confirmed to be exploitable; many simple bugs we fix do turn out to
232: have security consequences we could not predict. We do not have the
233: time resources to make these changes available in the above format.<p>
1.21 deraadt 234:
235: Thus there are usually minor security fixes in the current source code
236: beyond the previous major OpenBSD release. We make a limited
1.45 deraadt 237: guarantee that these problems are of minimal impact and unproven
1.44 ian 238: exploitability. If we discover that a problem definitely matters for
1.45 deraadt 239: security, patches will show up here <strong>VERY</strong> quickly.<p>
1.21 deraadt 240:
1.45 deraadt 241: People who are really concerned with security can do a number of
242: things:<p>
1.21 deraadt 243:
244: <ul>
245: <li>If you understand security issues, watch our
1.294 david 246: <a href="mail.html">source-changes mailing list</a> and keep an
1.23 deraadt 247: eye out for things which appear security related. Since
1.21 deraadt 248: exploitability is not proven for many of the fixes we make,
249: do not expect the relevant commit message to say "SECURITY FIX!".
250: If a problem is proven and serious, a patch will be available
251: here very shortly after.
1.161 horacio 252: <li>In addition to source changes, you can watch our <a href="mail.html">
1.160 ericj 253: security-announce mailing list</a> which will notify you for every
1.186 ian 254: security related item that the OpenBSD team deems as a possible threat,
1.160 ericj 255: and instruct you on how to patch the problem.
1.21 deraadt 256: <li>Track our current source code tree, and teach yourself how to do a
1.29 deraadt 257: complete system build from time to time (read /usr/src/Makefile
258: carefully). Users can make the assumption that the current
259: source tree always has stronger security than the previous release.
1.45 deraadt 260: However, building your own system from source code is not trivial;
1.424 ! tb 261: it is over 850MB of source code, and problems do occur as we
1.45 deraadt 262: transition between major releases.
1.115 ericj 263: <li>Install a binary snapshot for your
1.80 espie 264: architecture, which are made available fairly often. For
1.424 ! tb 265: instance, an amd64 snapshot is typically made available daily.
1.21 deraadt 266: </ul>
267:
1.9 deraadt 268: <p>
1.288 matthieu 269: <a name="reporting"></a>
1.294 david 270: <li><h3><font color="#e00000">Reporting problems</font></h3><p>
1.3 deraadt 271:
1.5 deraadt 272: <p> If you find a new security problem, you can mail it to
1.294 david 273: <a href="mailto:deraadt@openbsd.org">deraadt@openbsd.org</a>.
1.7 deraadt 274: <br>
1.5 deraadt 275: If you wish to PGP encode it (but please only do so if privacy is very
1.112 philen 276: urgent, since it is inconvenient) use this <a href="advisories/pgpkey.txt">pgp key</a>.
1.5 deraadt 277:
1.107 deraadt 278: <p>
1.288 matthieu 279: <a name="papers"></a>
1.294 david 280: <li><h3><font color="#e00000">Further Reading</font></h3><p>
1.107 deraadt 281:
1.389 lum 282: Numerous
1.404 deraadt 283: <a href="papers/index.html">papers</a> have been written by OpenBSD team members,
1.389 lum 284: many dedicated to security.
1.294 david 285: </ul>
1.1 deraadt 286:
1.24 deraadt 287: </body>
288: </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