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