Annotation of www/security.html, Revision 1.120
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">
1.45 deraadt 10: <meta name="copyright" content="This document copyright 1997,1998 by OpenBSD.">
1.1 deraadt 11: </head>
12:
13: <BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#23238E">
1.77 deraadt 14: <img alt="[OpenBSD]" height=30 width=141 SRC="images/smalltitle.gif">
1.106 deraadt 15: <p>
1.110 deraadt 16: <h2><font color=#e00000>Security</font><hr></h2>
1.1 deraadt 17:
1.114 philen 18: <table width="100%">
19: <tr>
20: <td colspan="2">
21: <strong>Index</strong>
22: </td>
23: </tr>
24: <tr>
25: <td valign="top">
1.106 deraadt 26: <a href=#goals>Security goals of the Project</a>.<br>
27: <a href=#disclosure>Full Disclosure policy</a>.<br>
28: <a href=#process>Source code auditing process</a>.<br>
1.111 aaron 29: <a href=#default>"Secure by Default"</a>.<br>
1.106 deraadt 30: <a href=#crypto>Use of Cryptography</a>.<br>
31: <p>
32: <a href=#watching>Watching changes</a>.<br>
33: <a href=#reporting>Reporting security issues</a>.<br>
1.107 deraadt 34: <a href=#papers>Further Reading</a><br>
1.106 deraadt 35: <p>
1.114 philen 36: </td>
37: <td valign="top">
1.119 deraadt 38: <a href="#26">For 2.6 security advisories</a>.<br>
1.114 philen 39: <a href="#25">For 2.5 security advisories</a>.<br>
40: <a href="#24">For 2.4 security advisories</a>.<br>
41: <a href="#23">For 2.3 security advisories</a>.<br>
42: <a href="#22">For 2.2 security advisories</a>.<br>
43: <a href="#21">For 2.1 security advisories</a>.<br>
44: <a href="#20">For 2.0 security advisories</a>.<br>
45: </td>
46: </tr>
47: </table>
1.56 deraadt 48: <hr>
49:
1.106 deraadt 50: <dl>
51: <a name=goals></a>
1.110 deraadt 52: <li><h3><font color=#e00000>Goal</font></h3><p>
1.22 deraadt 53:
1.14 deraadt 54: OpenBSD believes in strong security. Our aspiration is to be NUMBER
1.22 deraadt 55: ONE in the industry for security (if we are not already there). Our
56: open software development model permits us to take a more
57: uncompromising view towards increased security than Sun, SGI, IBM, HP,
58: or other vendors are able to. We can make changes the vendors would
1.27 deraadt 59: not make. Also, since OpenBSD is exported with <a href=crypto.html>
1.45 deraadt 60: cryptography</a>, we are able to take cryptographic approaches towards
61: fixing security problems.<p>
1.18 deraadt 62:
1.106 deraadt 63: <a name=disclosure></a>
1.110 deraadt 64: <li><h3><font color=#e00000>Full Disclosure</font></h3><p>
1.106 deraadt 65:
1.45 deraadt 66: Like many readers of the
1.102 deraadt 67: <a href=http://www.securityfocus.com/bugtraq/archive>
1.18 deraadt 68: BUGTRAQ mailing list</a>,
1.106 deraadt 69: we believe in full disclosure of security problems. In the
70: operating system arena, we were probably the first to embrace
71: the concept. Many vendors, even of free software, still try
72: to hide issues from their users.<p>
73:
74: Security information moves very fast in cracker circles. On the other
75: hand, our experience is that coding and releasing of proper security
76: fixes typically requires about an hour of work -- very fast fix
77: turnaround is possible. Thus we think that full disclosure helps the
78: people who really care about security.<p>
79:
1.111 aaron 80: <a name=process>
1.110 deraadt 81: <li><h3><font color=#e00000>Audit Process</font></h3><p>
1.15 deraadt 82:
1.12 deraadt 83: Our security auditing team typically has between six and twelve
1.45 deraadt 84: members who continue to search for and fix new security holes. We
85: have been auditing since the summer of 1996. The process we follow to
86: increase security is simply a comprehensive file-by-file analysis of
1.106 deraadt 87: every critical software component. We are not so much looking for
88: security holes, as we are looking for basic software bugs, and if
89: years later someone discovers a the problem used to be a security
90: issue, and we fixed it because it was just a bug, well, all the
91: better. Flaws have been found in just about every area of the system.
92: Entire new classes of security problems have been found during our
93: audit, and often source code which had been audited earlier needs
94: re-auditing with these new flaws in mind. Code often gets audited
95: multiple times, and by multiple people with different auditing
96: skills.<p>
1.12 deraadt 97:
1.94 deraadt 98: Some members of our security auditing team worked for Secure Networks,
99: the company that made the industry's premier network security scanning
100: software package Ballista (Secure Networks got purchased by Network
101: Associates, Ballista got renamed to Cybercop Scanner, and well...)
102: That company did a lot of security research, and thus fit in well
1.106 deraadt 103: with the OpenBSD stance. OpenBSD passed Ballista's tests with flying
104: colours since day 1.<p>
1.31 deraadt 105:
1.34 deraadt 106: Another facet of our security auditing process is its proactiveness.
1.45 deraadt 107: In most cases we have found that the determination of exploitability
108: is not an issue. During our ongoing auditing process we find many
109: bugs, and endeavor to fix them even though exploitability is not
110: proven. We fix the bug, and we move on to find other bugs to fix. We
111: have fixed many simple and obvious careless programming errors in code
112: and only months later discovered that the problems were in fact
113: exploitable. (Or, more likely someone on
1.102 deraadt 114: <a href=http://www.securityfocus.com/bugtraq/archive>BUGTRAQ</a>
1.45 deraadt 115: would report that other operating systems were vulnerable to a `newly
116: discovered problem', and then it would be discovered that OpenBSD had
117: been fixed in a previous release). In other cases we have been saved
118: from full exploitability of complex step-by-step attacks because we
119: had fixed one of the intermediate steps. An example of where we
1.94 deraadt 120: managed such a success is the lpd advisory that Secure Networks put out.
121: <p>
1.29 deraadt 122:
1.110 deraadt 123: <li><h3><font color=#e00000>The Reward</font></h3><p>
1.106 deraadt 124:
1.45 deraadt 125: Our proactive auditing process has really paid off. Statements like
1.35 deraadt 126: ``This problem was fixed in OpenBSD about 6 months ago'' have become
1.45 deraadt 127: commonplace in security forums like
1.102 deraadt 128: <a href=http://www.securityfocus.com/bugtraq/archive>BUGTRAQ</a>.<p>
1.35 deraadt 129:
1.45 deraadt 130: The most intense part of our security auditing happened immediately
1.80 espie 131: before the OpenBSD 2.0 release and during the 2.0->2.1 transition,
1.45 deraadt 132: over the last third of 1996 and first half of 1997. Thousands (yes,
133: thousands) of security issues were fixed rapidly over this year-long
134: period; bugs like the standard buffer overflows, protocol
135: implementation weaknesses, information gathering, and filesystem
136: races. Hence most of the security problems that we encountered were
137: fixed before our 2.1 release, and then a far smaller number needed
138: fixing for our 2.2 release. We do not find as many problems anymore,
139: it is simply a case of diminishing returns. Recently the security
140: problems we find and fix tend to be significantly more obscure or
141: complicated. Still we will persist for a number of reasons:<p>
1.36 deraadt 142:
1.35 deraadt 143: <ul>
1.45 deraadt 144: <li>Occasionally we find a simple problem we missed earlier. Doh!
1.35 deraadt 145: <li>Security is like an arms race; the best attackers will continue
1.45 deraadt 146: to search for more complicated exploits, so we will too.
147: <li>Finding and fixing subtle flaws in complicated software is
148: a lot of fun.
1.35 deraadt 149: </ul>
1.106 deraadt 150: <p>
1.15 deraadt 151:
1.14 deraadt 152: The auditing process is not over yet, and as you can see we continue
1.28 deraadt 153: to find and fix new security flaws.<p>
1.12 deraadt 154:
1.106 deraadt 155: <a name=default></a>
1.110 deraadt 156: <li><h3><font color=#e00000>"Secure by Default"</font></h3><p>
1.106 deraadt 157:
158: To ensure that novice users of OpenBSD do not need to become security
159: experts overnight (a viewpoint which other vendors seem to have), we
160: ship the operating system in a Secure by Default mode. All non-essential
161: services are disabled. As the user/administrator becomes more familiar
162: with the system, he will discover that he has to enable daemons and other
163: parts of the system. During the process of learning how to enable a new
164: service, the novice is more likely to learn of security considerations.<p>
165:
166: This is in stark contrast to the increasing number of systems that
167: ship with NFS, mountd, web servers, and various other services enabled
168: by default, creating instantaneous security problems for their users
169: within minutes after their first install.<p>
170:
1.111 aaron 171: <a name=crypto>
1.110 deraadt 172: <li><h3><font color=#e00000>Cryptography</font></h3><p>
1.106 deraadt 173:
174: And of course, since the OpenBSD project is based in Canada, it is possible
175: for us to integrate cryptography. For more information, read the page
1.116 deraadt 176: outlining <a href=crypto.html>what we have done with cryptography</a>.</p>
1.106 deraadt 177:
1.110 deraadt 178: <li><h3><font color=#e00000>Advisories</font></h3><p>
1.106 deraadt 179:
180: <dl>
181:
182: <li>
1.119 deraadt 183: <a name=26></a>
184:
185: <h3><font color=#e00000>OpenBSD 2.6 Security Advisories</font></h3>
186: These are the OpenBSD 2.6 advisories -- all these problems are solved
187: in <a href=anoncvs.html>OpenBSD current</a>. Obviously, all the
188: OpenBSD 2.5 advisories listed below are fixed in OpenBSD 2.6.
189:
190: <p>
191: <ul>
192: <li><a href=errata.html#ifmedia>Nov 9, 1999:
193: Any user could change interface media configurations
194: (patch included).</a>
1.120 ! deraadt 195: <li><a href=errata.html#sslUSA>Dec 2, 1999:
! 196: A buffer overflow in the RSAREF code included in the
! 197: USA version of libssl, is possibly exploitable in
! 198: httpd, ssh, or isakmpd, if SSL/RSA features are enabled.
! 199: (patch included).</a>
1.119 deraadt 200: </ul>
201:
202: <p>
203: <li>
204:
1.93 deraadt 205: <a name=25></a>
1.106 deraadt 206:
1.110 deraadt 207: <h3><font color=#e00000>OpenBSD 2.5 Security Advisories</font></h3>
1.93 deraadt 208: These are the OpenBSD 2.5 advisories -- all these problems are solved
209: in <a href=anoncvs.html>OpenBSD current</a>. Obviously, all the
210: OpenBSD 2.4 advisories listed below are fixed in OpenBSD 2.5.
211:
1.96 deraadt 212: <p>
1.104 deraadt 213: <ul>
1.117 deraadt 214: <li><a href=errata25.html#cron>Aug 30, 1999:
1.103 deraadt 215: In cron(8), make sure argv[] is NULL terminated in the
216: fake popen() and run sendmail as the user, not as root.
217: (patch included).</a>
1.117 deraadt 218: <li><a href=errata25.html#miscfs>Aug 12, 1999: The procfs and fdescfs
1.101 deraadt 219: filesystems had an overrun in their handling of uio_offset
220: in their readdir() routines. (These filesystems are not
221: enabled by default). (patch included).</a>
1.117 deraadt 222: <li><a href=errata25.html#profil>Aug 9, 1999: Stop profiling (see profil(2))
1.100 deraadt 223: when we execve() a new process. (patch included).</a>
1.117 deraadt 224: <li><a href=errata25.html#ipsec_in_use>Aug 6, 1999: Packets that should have
1.98 deraadt 225: been handled by IPsec may be transmitted as cleartext.
226: PF_KEY SA expirations may leak kernel resources.
227: (patch included).</a>
1.117 deraadt 228: <li><a href=errata25.html#rc>Aug 5, 1999: In /etc/rc, use mktemp(1) for
1.97 deraadt 229: motd re-writing and change the find(1) to use -execdir
230: (patch included).</a>
1.117 deraadt 231: <li><a href=errata25.html#chflags>Jul 30, 1999: Do not permit regular
1.95 deraadt 232: users to chflags(2) or fchflags(2) on character or block devices
233: which they may currently be the owner of (patch included).</a>
1.117 deraadt 234: <li><a href=errata25.html#nroff>Jul 27, 1999: Cause groff(1) to be invoked
1.95 deraadt 235: with the -S flag, when called by nroff(1) (patch included).</a>
1.93 deraadt 236: </ul>
237:
1.106 deraadt 238: <p>
239: <li>
1.75 deraadt 240: <a name=24></a>
1.110 deraadt 241: <h3><font color=#e00000>OpenBSD 2.4 Security Advisories</font></h3>
1.75 deraadt 242: These are the OpenBSD 2.4 advisories -- all these problems are solved
243: in <a href=anoncvs.html>OpenBSD current</a>. Obviously, all the
244: OpenBSD 2.3 advisories listed below are fixed in OpenBSD 2.4.
245:
1.96 deraadt 246: <p>
1.75 deraadt 247: <ul>
1.92 deraadt 248: <li><a href=errata24.html#poll>Mar 22, 1999: The nfds argument for poll(2) needs
1.91 deraadt 249: to be constrained, to avoid kvm starvation (patch included).</a>
1.92 deraadt 250: <li><a href=errata24.html#tss>Mar 21, 1999: A change in TSS handling stops
1.91 deraadt 251: another kernel crash case caused by the <strong>crashme</strong>
252: program (patch included).</a>
1.92 deraadt 253: <li><a href=errata24.html#nlink>Feb 25, 1999: An unbounded increment on the
1.90 deraadt 254: nlink value in FFS and EXT2FS filesystems can cause a system crash.
1.89 deraadt 255: (patch included).</a>
1.92 deraadt 256: <li><a href=errata24.html#ping>Feb 23, 1999: Yet another buffer overflow
1.88 deraadt 257: existed in ping(8). (patch included).</a>
1.92 deraadt 258: <li><a href=errata24.html#ipqrace>Feb 19, 1999: ipintr() had a race in use of
1.87 deraadt 259: the ipq, which could permit an attacker to cause a crash.
260: (patch included).</a>
1.92 deraadt 261: <li><a href=errata24.html#accept>Feb 17, 1999: A race condition in the
1.86 deraadt 262: kernel between accept(2) and select(2) could permit an attacker
263: to hang sockets from remote.
264: (patch included).</a>
1.92 deraadt 265: <li><a href=errata24.html#maxqueue>Feb 17, 1999: IP fragment assembly can
1.85 deraadt 266: bog the machine excessively and cause problems.
267: (patch included).</a>
1.92 deraadt 268: <li><a href=errata24.html#trctrap>Feb 12, 1999: i386 T_TRCTRAP handling and
1.84 deraadt 269: DDB interacted to possibly cause a crash.
270: (patch included).</a>
1.92 deraadt 271: <li><a href=errata24.html#rst>Feb 11, 1999: TCP/IP RST handling was sloppy.
1.83 deraadt 272: (patch included).</a>
1.92 deraadt 273: <li><a href=errata24.html#bootpd>Nov 27, 1998: There is a remotely exploitable
1.81 deraadt 274: problem in bootpd(8). (patch included).</a>
1.92 deraadt 275: <li><a href=errata24.html#termcap>Nov 19, 1998: There is a possibly locally
1.82 deraadt 276: exploitable problem relating to environment variables in termcap
277: and curses. (patch included).</a>
1.92 deraadt 278: <li><a href=errata24.html#tcpfix>Nov 13, 1998: There is a remote machine lockup
1.78 deraadt 279: bug in the TCP decoding kernel. (patch included).</a>
1.75 deraadt 280: </ul>
281:
1.106 deraadt 282: <p>
283: <li>
1.58 deraadt 284: <a name=23></a>
1.110 deraadt 285: <h3><font color=#e00000>OpenBSD 2.3 Security Advisories</font></h3>
1.73 deraadt 286: These are the OpenBSD 2.3 advisories -- all these problems are solved
287: in <a href=anoncvs.html>OpenBSD current</a>. Obviously, all the
288: OpenBSD 2.2 advisories listed below are fixed in OpenBSD 2.3.
1.53 matthieu 289:
1.96 deraadt 290: <p>
1.53 matthieu 291: <ul>
1.81 deraadt 292: <li><a href=errata23.html#bootpd>Nov 27, 1998: There is a remotely exploitable
293: problem in bootpd(8). (patch included).</a>
1.78 deraadt 294: <li><a href=errata23.html#tcpfix>Nov 13, 1998: There is a remote machine lockup
295: bug in the TCP decoding kernel. (patch included).</a>
1.76 aaron 296: <li><a href=errata23.html#fdalloc>Jul 2, 1998: setuid and setgid processes
1.72 deraadt 297: should not be executed with fd slots 0, 1, or 2 free.
298: (patch included).</a>
1.79 deraadt 299: <li><a href=errata23.html#resolver>August 31, 1998: A benign looking resolver buffer overflow bug was re-introduced accidentally (patches included).</a>
1.76 aaron 300: <li><a href=errata23.html#xlib>June 6, 1998: Further problems with the X
1.71 deraadt 301: libraries (patches included).</a>
1.76 aaron 302: <li><a href=errata23.html#pctr>June 4, 1998: on non-Intel i386 machines, any user
1.72 deraadt 303: can use pctr(4) to crash the machine.</a>
1.76 aaron 304: <li><a href=errata23.html#kill>May 17, 1998: kill(2) of setuid/setgid target
1.66 deraadt 305: processes too permissive (4th revision patch included).</a>
1.76 aaron 306: <li><a href=errata23.html#immutable>May 11, 1998: mmap() permits partial bypassing
1.60 deraadt 307: of immutable and append-only file flags. (patch included).</a>
1.76 aaron 308: <li><a href=errata23.html#xterm-xaw>May 1, 1998: Buffer overflow in xterm and Xaw
1.58 deraadt 309: (CERT advisory VB-98.04) (patch included).</a>
1.76 aaron 310: <li><a href=errata23.html#ipsec>May 5, 1998: Incorrect handling of IPSEC packets
1.59 deraadt 311: if IPSEC is enabled (patch included).</a>
1.53 matthieu 312: </ul>
1.9 deraadt 313:
1.106 deraadt 314: <p>
315: <li>
1.58 deraadt 316: <a name=22></a>
1.110 deraadt 317: <h3><font color=#e00000>OpenBSD 2.2 Security Advisories</font></h3>
1.45 deraadt 318: These are the OpenBSD 2.2 advisories. All these problems are solved
1.55 deraadt 319: in <a href=23.html>OpenBSD 2.3</a>. Some of these problems
1.45 deraadt 320: still exist in other operating systems. (The supplied patches are for
321: OpenBSD 2.2; they may or may not work on OpenBSD 2.1).
1.9 deraadt 322:
1.96 deraadt 323: <p>
1.9 deraadt 324: <ul>
1.72 deraadt 325: <li><a href=errata22.html#ipsec>May 5, 1998: Incorrect handling of IPSEC
326: packets if IPSEC is enabled (patch included).</a>
327: <li><a href=errata22.html#xterm-xaw>May 1, 1998: Buffer overflow in xterm
328: and Xaw (CERT advisory VB-98.04) (patch included).</a>
329: <li><a href=errata22.html#uucpd>Apr 22, 1998: Buffer overflow in uucpd
330: (patch included).</a>
331: <li><a href=errata22.html#rmjob>Apr 22, 1998: Buffer mismanagement in lprm
332: (patch included).</a>
333: <li><a href=errata22.html#ping>Mar 31, 1998: Overflow in ping -R (patch included).</a>
334: <li><a href=errata22.html#named>Mar 30, 1998: Overflow in named fake-iquery
1.59 deraadt 335: (patch included).</a>
1.72 deraadt 336: <li><a href=errata22.html#mountd>Mar 2, 1998: Accidental NFS filesystem
337: export (patch included).</a>
1.112 philen 338: <li><a href="advisories/mmap.txt">Feb 26, 1998: Read-write mmap() flaw.</a>
1.72 deraadt 339: Revision 3 of the patch is available <a href=errata22.html#mmap>here</a>
1.112 philen 340: <li><a href="advisories/sourceroute.txt">Feb 19, 1998: Sourcerouted Packet
1.59 deraadt 341: Acceptance.</a>
1.50 deraadt 342: A patch is available <a href=errata22.html#sourceroute>here</a>.
1.72 deraadt 343: <li><a href=errata22.html#ruserok>Feb 13, 1998: Setuid coredump & Ruserok()
344: flaw (patch included).</a>
345: <li><a href=errata22.html#ldso>Feb 9, 1998: MIPS ld.so flaw (patch included).</a>
346: <li><a href=errata22.html#f00f>Dec 10, 1997: Intel P5 f00f lockup
1.59 deraadt 347: (patch included).</a>
1.1 deraadt 348: </ul>
349:
1.106 deraadt 350: <p>
351: <li>
1.58 deraadt 352: <a name=21></a>
1.110 deraadt 353: <h3><font color=#e00000>OpenBSD 2.1 Security Advisories</font></h3>
1.52 deraadt 354: These are the OpenBSD 2.1 advisories. All these problems are solved
355: in <a href=22.html>OpenBSD 2.2</a>. Some of these problems still
356: exist in other operating systems. (If you are running OpenBSD 2.1, we
357: would strongly recommend an upgrade to the newest release, as this
358: patch list only attempts at fixing the most important security
359: problems. In particular, OpenBSD 2.2 fixes numerous localhost
360: security problems. Many of those problems were solved in ways which
361: make it hard for us to provide patches).
362:
1.96 deraadt 363: <p>
1.52 deraadt 364: <ul>
1.112 philen 365: <li><a href="advisories/signals.txt">Sep 15, 1997: Deviant Signals (patch included)</a>
366: <li><a href="advisories/rfork.txt">Aug 2, 1997: Rfork() system call flaw
1.59 deraadt 367: (patch included)</a>
1.112 philen 368: <li><a href="advisories/procfs.txt">Jun 24, 1997: Procfs flaws (patch included)</a>
1.52 deraadt 369: </ul>
1.51 deraadt 370:
1.106 deraadt 371: <p>
372: <li>
373: <a name=20></a>
1.110 deraadt 374: <h3><font color=#e00000>OpenBSD 2.0 Security Advisories</font></h3>
1.99 deraadt 375: These are the OpenBSD 2.0 advisories. All these problems are solved
376: in <a href=21.html>OpenBSD 2.1</a>. Some of these problems still
377: exist in other operating systems. (If you are running OpenBSD 2.0, we
378: commend you for being there back in the old days!, but you're really
379: missing out if you don't install a new version!)
380:
381: <p>
382: <ul>
1.112 philen 383: <li><a href="advisories/res_random.txt">April 22, 1997: Predictable IDs in the
1.99 deraadt 384: resolver (patch included)</a>
385: <li>Many others... if people can hunt them down, please let me know
386: and we'll put them up here.
387: </ul>
388:
1.106 deraadt 389: </dl>
1.51 deraadt 390: <p>
1.106 deraadt 391:
392: <a name=watching></a>
1.110 deraadt 393: <li><h3><font color=#e00000>Watching our Changes</font></h3><p>
1.106 deraadt 394:
1.21 deraadt 395: Since we take a proactive stance with security, we are continually
396: finding and fixing new security problems. Not all of these problems
1.80 espie 397: get widely reported because (as stated earlier) many of them are not
1.45 deraadt 398: confirmed to be exploitable; many simple bugs we fix do turn out to
399: have security consequences we could not predict. We do not have the
400: time resources to make these changes available in the above format.<p>
1.21 deraadt 401:
402: Thus there are usually minor security fixes in the current source code
403: beyond the previous major OpenBSD release. We make a limited
1.45 deraadt 404: guarantee that these problems are of minimal impact and unproven
1.44 ian 405: exploitability. If we discover that a problem definitely matters for
1.45 deraadt 406: security, patches will show up here <strong>VERY</strong> quickly.<p>
1.21 deraadt 407:
1.45 deraadt 408: People who are really concerned with security can do a number of
409: things:<p>
1.21 deraadt 410:
411: <ul>
412: <li>If you understand security issues, watch our
1.27 deraadt 413: <a href=mail.html>source-changes mailing list</a> and keep an
1.23 deraadt 414: eye out for things which appear security related. Since
1.21 deraadt 415: exploitability is not proven for many of the fixes we make,
416: do not expect the relevant commit message to say "SECURITY FIX!".
417: If a problem is proven and serious, a patch will be available
418: here very shortly after.
419: <li>Track our current source code tree, and teach yourself how to do a
1.29 deraadt 420: complete system build from time to time (read /usr/src/Makefile
421: carefully). Users can make the assumption that the current
422: source tree always has stronger security than the previous release.
1.45 deraadt 423: However, building your own system from source code is not trivial;
424: it is nearly 300MB of source code, and problems do occur as we
425: transition between major releases.
1.115 ericj 426: <li>Install a binary snapshot for your
1.80 espie 427: architecture, which are made available fairly often. For
1.29 deraadt 428: instance, an i386 snapshot is typically made available weekly.
1.21 deraadt 429: </ul>
430:
1.9 deraadt 431: <p>
1.111 aaron 432: <a name=reporting>
1.110 deraadt 433: <li><h3><font color=#e00000>Reporting problems</font></h3><p>
1.3 deraadt 434:
1.5 deraadt 435: <p> If you find a new security problem, you can mail it to
1.6 deraadt 436: <a href=mailto:deraadt@openbsd.org>deraadt@openbsd.org</a>.
1.7 deraadt 437: <br>
1.5 deraadt 438: If you wish to PGP encode it (but please only do so if privacy is very
1.112 philen 439: urgent, since it is inconvenient) use this <a href="advisories/pgpkey.txt">pgp key</a>.
1.5 deraadt 440:
1.107 deraadt 441: <p>
442: <a name=papers></a>
1.110 deraadt 443: <li><h3><font color=#e00000>Further Reading</font></h3><p>
1.107 deraadt 444:
445: A number of papers have been written by OpenBSD team members, about security
446: related changes they have done in OpenBSD. The postscript versions of these
1.108 deraadt 447: documents are available as follows.<p>
1.107 deraadt 448:
449: <ul>
1.113 deraadt 450: <li>A Future-Adaptable Password Scheme.<br>
1.118 deraadt 451: <a href=events.html#usenix99>Usenix 1999</a>,
1.113 deraadt 452: by <a href=mailto:provos@openbsd.org>Niels Provos<a/>,
453: <a href=mailto:dm@openbsd.org>David Mazieres</a>.<br>
1.107 deraadt 454: <a href=papers/bcrypt-paper.ps>paper</a> and
455: <a href=papers/bcrypt-slides.ps>slides</a>.
1.113 deraadt 456: <p>
457: <li>Cryptography in OpenBSD: An Overview.<br>
1.118 deraadt 458: <a href=events.html#usenix99>Usenix 1999</a>,
1.113 deraadt 459: by <a href=mailto:deraadt@openbsd.org>Theo de Raadt</a>,
460: <a href=mailto:niklas@openbsd.org>Niklas Hallqvist</a>,
461: <a href=mailto:art@openbsd.org>Artur Grabowski</a>,
462: <a href=mailto:angelos@openbsd.org>Angelos D. Keromytis</a>,
463: <a href=mailto:provos@openbsd.org>Niels Provos</a>.<br>
1.107 deraadt 464: <a href=papers/crypt-paper.ps>paper</a> and
465: <a href=papers/crypt-slides.ps>slides</a>.
1.113 deraadt 466: <p>
467: <li>strlcpy and strlcat -- consistent, safe, string copy and concatenation.<br>
1.118 deraadt 468: <a href=events.html#usenix99>Usenix 1999</a>,
1.113 deraadt 469: by <a href=mailto:millert@openbsd.org>Todd C. Miller</a>,
470: <a href=mailto:deraadt@openbsd.org>Theo de Raadt</a>.<br>
1.109 deraadt 471: <a href=papers/strlcpy-paper.ps>paper</a> and
472: <a href=papers/strlcpy-slides.ps>slides</a>.
1.113 deraadt 473: <p>
1.118 deraadt 474: <li>Dealing with Public Ethernet Jacks-Switches, Gateways, and Authentication.<br>
475: <a href=events.html#lisa99>LISA 1999</a>,
476: by <a href=mailto:beck@openbsd.org>Bob Beck</a>.<br>
477: <a href=papers/authgw-paper.ps>paper</a> and
478: <a href=papers/authgw-slides.ps>slides</a>.
479: <p>
1.107 deraadt 480: </ul>
481:
1.106 deraadt 482: </dl>
483:
1.2 deraadt 484: <hr>
1.68 pauls 485: <a href=index.html><img height=24 width=24 src=back.gif border=0 alt=OpenBSD></a>
1.24 deraadt 486: <a href=mailto:www@openbsd.org>www@openbsd.org</a>
487: <br>
1.120 ! deraadt 488: <small>$OpenBSD: security.html,v 1.119 1999/11/27 16:34:44 deraadt Exp $</small>
1.1 deraadt 489:
1.24 deraadt 490: </body>
491: </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