Annotation of www/errata23.html, Revision 1.60
1.28 naddy 1: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
1.1 deraadt 2: <html>
3: <head>
1.12 deraadt 4: <title>OpenBSD 2.3 errata</title>
1.1 deraadt 5: <meta name="resource-type" content="document">
6: <meta name="description" content="the OpenBSD CD errata page">
7: <meta name="keywords" content="openbsd,cd,errata">
8: <meta name="distribution" content="global">
1.18 jufi 9: <meta name="copyright" content="This document copyright 1997-2001 by OpenBSD.">
1.31 henning 10: <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
1.1 deraadt 11: </head>
12:
1.32 david 13: <body bgcolor="#ffffff" text="#000000" link="#23238E">
1.1 deraadt 14:
1.23 jsyn 15: <a href="index.html"><img alt="[OpenBSD]" height="30" width="141" src="images/smalltitle.gif" border="0"></a>
1.28 naddy 16: <h2><font color="#0000e0">
1.4 espie 17: This is the OpenBSD 2.3 release errata & patch list:
1.1 deraadt 18:
19: </font></h2>
20:
21: <hr>
1.13 jason 22: <a href=stable.html>For OpenBSD patch branch information, please refer here.</a><br>
1.25 deraadt 23: <br>
1.26 deraadt 24: For errata on a certain release, click below:<br>
1.25 deraadt 25: <a href="errata21.html">2.1</a>,
26: <a href="errata22.html">2.2</a>,
27: <a href="errata24.html">2.4</a>,
28: <a href="errata25.html">2.5</a>,
29: <a href="errata26.html">2.6</a>,
30: <a href="errata27.html">2.7</a>,
31: <a href="errata28.html">2.8</a>,
32: <a href="errata29.html">2.9</a>,
33: <a href="errata30.html">3.0</a>,
34: <a href="errata31.html">3.1</a>,
1.29 deraadt 35: <a href="errata32.html">3.2</a>,
1.30 david 36: <a href="errata33.html">3.3</a>,
1.34 david 37: <a href="errata34.html">3.4</a>,
1.35 miod 38: <a href="errata35.html">3.5</a>,
1.36 deraadt 39: <a href="errata36.html">3.6</a>,
1.60 ! deraadt 40: <a href="errata37.html">3.7</a>,
1.45 deraadt 41: <br>
1.38 deraadt 42: <a href="errata38.html">3.8</a>,
1.39 deraadt 43: <a href="errata39.html">3.9</a>,
1.40 deraadt 44: <a href="errata40.html">4.0</a>,
1.42 merdely 45: <a href="errata41.html">4.1</a>,
1.44 deraadt 46: <a href="errata42.html">4.2</a>,
1.45 deraadt 47: <a href="errata43.html">4.3</a>,
1.47 deraadt 48: <a href="errata44.html">4.4</a>,
1.48 deraadt 49: <a href="errata45.html">4.5</a>,
1.49 deraadt 50: <a href="errata46.html">4.6</a>,
1.51 deraadt 51: <a href="errata47.html">4.7</a>,
1.52 miod 52: <a href="errata48.html">4.8</a>,
1.53 nick 53: <a href="errata49.html">4.9</a>,
1.54 sthen 54: <a href="errata50.html">5.0</a>,
1.55 deraadt 55: <a href="errata51.html">5.1</a>,
1.56 deraadt 56: <a href="errata52.html">5.2</a>,
1.57 deraadt 57: <a href="errata53.html">5.3</a>,
1.60 ! deraadt 58: <br>
1.58 deraadt 59: <a href="errata54.html">5.4</a>,
60: <a href="errata55.html">5.5</a>.
1.25 deraadt 61: <br>
1.1 deraadt 62: <hr>
63:
1.50 sthen 64: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3.tar.gz">
1.1 deraadt 65: You can also fetch a tar.gz file containing all the following patches</a>.
66: This file is updated once a day.
67:
1.14 ericj 68: <p>
1.27 deraadt 69: For more detailed information on how to install patches to OpenBSD, please
1.14 ericj 70: consult the <a href="./faq/faq10.html#10.14">OpenBSD FAQ</a>.
71:
1.1 deraadt 72: <hr>
73:
1.31 henning 74: <a name="all"></a>
75: <h3><font color="#e00000">All architectures</font></h3>
1.1 deraadt 76: <ul>
1.31 henning 77: <li><a name="bootpd"></a>
78: <font color="#009000"><strong>SECURITY FIX</strong></font><br>
1.5 deraadt 79: A remotely exploitable problem exists in bootpd(8). bootpd is disabled
80: by default, but some people may actually be using it.
1.50 sthen 81: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/bootpd.patch">
1.58 deraadt 82: A source code patch exists which remedies this problem</a>, this is the
1.7 millert 83: second version of the patch.
1.5 deraadt 84: <p>
1.31 henning 85: <li><a name="tcpfix"></a>
86: <font color="#009000"><strong>SECURITY FIX</strong></font><br>
1.2 deraadt 87: A remote machine lockup problem exists in the TCP decoding code.
1.50 sthen 88: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/tcpfix.patch">
1.2 deraadt 89: A source code patch exists which remedies this problem.</a>
90: <p>
1.31 henning 91: <li><a name="atapi"></a>
92: <font color="#009000"><strong>HARDWARE SUPPORT</strong></font><br>
1.1 deraadt 93: Some ATAPI cdroms which do not support the full mandatory command set,
94: (e.g. ATAPI_READ_CD_CAPACITY) do not work with the acd(4) driver.
95: A patch is
1.50 sthen 96: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/acd.patch">
1.1 deraadt 97: available here.</a>
98: <p>
1.31 henning 99: <li><a name="chpass"></a>
100: <font color="#009000"><strong>SECURITY FIX</strong></font><br>
1.1 deraadt 101: Chpass(1) has a file descriptor leak which allows an
102: attacker to modify /etc/master.passwd.
1.50 sthen 103: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/chpass.patch">
1.1 deraadt 104: A source code patch exists which remedies this problem.</a>
105: <p>
1.31 henning 106: <li><a name="resid"></a>
107: <font color="#009000"><strong>RELIABILITY FIX</strong></font><br>
1.43 tobias 108: Calling readv(2) with iov_len < 0 or > INT_MAX would result in a
1.1 deraadt 109: kernel panic. This is the third revision of this patch.
1.50 sthen 110: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/resid.patch">
1.1 deraadt 111: A source code patch exists which remedies this problem.</a>
112: <p>
1.31 henning 113: <li><a name="inetd"></a>
114: <font color="#009000"><strong>SECURITY FIX</strong></font><br>
1.1 deraadt 115: Inetd had a file descriptor leak. A patch is
1.50 sthen 116: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/inetd.patch">
1.1 deraadt 117: available here.</a>
118: <p>
1.31 henning 119: <li><a name="unionfs"></a>
120: <font color="#009000"><strong>BUG FIX</strong></font><br>
1.1 deraadt 121: As shipped, unionfs had some serious problems.
1.50 sthen 122: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/unionfs.patch">
1.1 deraadt 123: A patch is available to solve this</a>.
124: <p>
1.31 henning 125: <li><a name="fdalloc"></a>
126: <font color="#009000"><strong>SECURITY FIX</strong></font><br>
1.1 deraadt 127: Some non-allocated file descriptors have implied uses according to
128: system libraries, and hence setuid and setgid processes should not
129: be executed with these descriptors unallocated. A patch which forces
130: setuid and setgid processes to have some descriptors in fd slots
1.58 deraadt 131: 0, 1, and 2 is
1.50 sthen 132: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/fdalloc.patch">
1.1 deraadt 133: available here.</a>
134: <p>
1.31 henning 135: <li><a name="resolver"></a>
136: <font color="#009000"><strong>SECURITY FIX</strong></font><br>
1.3 deraadt 137: A benign looking buffer overflow in the resolver routines was re-introduced
138: accidentally. The previously fixed behaviour is more correct. A patch
139: to fix this is
1.50 sthen 140: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/resolver.patch">
1.3 deraadt 141: available here.</a>
142: <p>
1.31 henning 143: <li><a name="xlib"></a>
144: <font color="#009000"><strong>SECURITY FIX</strong></font><br>
1.1 deraadt 145: Vulnerabilities have been found in the X11, Xt, Xaw and Xmu
146: libraries. These affect xterm and all other setuid-root programs that
147: use these libraries. The problems are associated with buffer overflows
148: in code that processes user-supplied data. The Xt library problems
149: include those fixed in TOG's recent public patch 3 for X11R6.3. All
150: releases of XFree86 up to and including 3.3.2 patch 1 and the version
151: distributed with OpenBSD are vulnerable to some or all of these
152: problems.
153: These problems are fixed in XFree86 patch 2.
1.50 sthen 154: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/XFree86-3.3.2.2.patch">
1.1 deraadt 155: The 2nd source patch</a> for these problems, specifically adapted to the
156: OpenBSD 2.3 X11 tree, is available now.
157: <p>
1.31 henning 158: <li><a name="kill"></a>
159: <font color="#009000"><strong>SECURITY FIX</strong></font><br>
1.1 deraadt 160: The kill(2) system call previously would permit a large set of signals to
161: be delivered to setuid or setgid processes. If such processes were using
162: those signals in dubious ways, this could have resulted in security
163: problems of various kinds.
1.50 sthen 164: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/kill.patch">
1.1 deraadt 165: The fourth revision of a source code patch which solves the problem is
166: available.</a>
167: <p>
1.31 henning 168: <li><a name="immutable"></a>
169: <font color="#009000"><strong>SECURITY FIX</strong></font><br>
1.1 deraadt 170: A possible new security problem exists if you rely on securelevels and
171: immutable or append-only files or character devices. The fix does not
172: permit mmap'ing of immutable or append-only files which are otherwise
1.17 pvalchev 173: writable, as the VM system will bypass the meaning of the file flags
1.1 deraadt 174: when writes happen to the file.
1.50 sthen 175: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/immutable.patch">
1.1 deraadt 176: A source code patch exists which remedies this problem.</a>
177: <p>
1.31 henning 178: <li><a name="ipsec"></a>
179: <font color="#009000"><strong>SECURITY FIX</strong></font><br>
1.1 deraadt 180: If IPSEC communication is attempted by starting photurisd(8) (which is
181: disabled by default), a system crash may be evoked from remote if
182: an attacker uses some classes of invalid packets.
1.50 sthen 183: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/ipsec.patch">
1.1 deraadt 184: A source code patch exists which remedies this problem.</a>
185: <p>
1.31 henning 186: <a name="xterm-xaw"></a>
1.28 naddy 187: <li><font color="#009000"><strong>SECURITY FIX</strong></font><br>
1.1 deraadt 188: As stated in CERT advisory VB-98.04, there are buffer
189: overrun problems in <strong>xterm</strong> related to the input-Method,
190: preeditType, and *Keymap resources. Additional buffer overruns exist in
191: the <strong>Xaw</strong> library related to the inputMethod and
192: preeditType resources. The xterm(1) problem represents a security
193: vulnerability for any platform where xterm is installed setuid-root
194: (as is the case for all OpenBSD platforms). The Xaw problem represents
195: a security vulnerability for any setuid-root program that uses the Xaw
196: library (including xterm). Patch1 from XFree86 3.3.2 corrects
197: these problems.
1.50 sthen 198: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/xterm-xaw.patch">
1.1 deraadt 199: We provide a version of this patch file specifically for the OpenBSD 2.3 tree</a>.
200: We also provide tar files which replace the xterm(1) binary and the libXaw
201: libraries on your system. These are expected to be extracted in
202: <strong>/usr/X11R6</strong> using the command
203: <strong>"tar xvfpz Xawfix.tgz"</strong>.
204: The files are...
1.50 sthen 205: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/i386/Xawfix.tgz">i386</a>,
206: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/alpha/Xawfix.tgz">alpha</a>,
207: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/mac68k/Xawfix.tgz">mac68k</a>,
208: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/mvme68k/Xawfix.tgz">
1.1 deraadt 209: mvme68k</a>,
1.50 sthen 210: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/hp300/Xawfix.tgz">hp300</a>,
211: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/sparc/Xawfix.tgz">sparc</a>,
212: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/pmax/Xawfix.tgz">pmax</a>,
1.1 deraadt 213: and
1.50 sthen 214: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/arc/Xawfix.tgz">arc</a>.
1.1 deraadt 215: <p>
216: </ul>
1.31 henning 217: <a name="i386"></a>
218: <h3><font color="#e00000">i386</font></h3>
1.1 deraadt 219: <ul>
1.31 henning 220: <li><a name="pctr"></a>
221: <font color="#009000"><strong>RELIABILITY FIX</strong></font><br>
1.1 deraadt 222: The pctr(4) driver has bugs that permit any user to crash the machine,
223: if the CPU is not an Intel CPU. This problem has been properly fixed
224: since, but fixes are hard to apply to the 2.2 or 2.3 releases. To avoid
225: the problem, recompile your kernel without the pctr(4) device driver.
226: <p>
1.28 naddy 227: <li><font color="#009000"><strong>CORRUPTED FILE</strong></font><br>
1.1 deraadt 228: The CD version of the precompiled ghostscript package is corrupted and
229: not installable. The correct file can be retrieved by FTP from:
1.50 sthen 230: <a href="http://ftp.openbsd.org/pub/OpenBSD/2.3/packages/i386/ghostscript-5.10.tgz">
231: http://ftp.openbsd.org/pub/OpenBSD/2.3/packages/i386/ghostscript-5.10.tgz</a>.
1.1 deraadt 232: Its checksums (obtained with <i>cksum(1)</i>, <i>md5(1)</i> and
233: <i>sha1(1)</i> respectively) are:
234: <ul>
235: <li>725752890 3639338 ghostscript-5.10.tgz
236: <li>MD5 (ghostscript-5.10.tgz) = 3144ca814ad1965d671be2b7be3d3050
237: <li>SHA1 (ghostscript-5.10.tgz) = bd9374fa547ac0078d5207463d3b0a19d80d213c
238: </ul>
239: <p>
1.31 henning 240: <a name="pcvt"></a>
1.28 naddy 241: <li><font color="#009000"><strong>RELIABILITY FIX</strong></font><br>
1.1 deraadt 242: The pcvt(4) console driver has a bug that can cause some keyboard
243: controllers to lock up when a key is pressed that toggles the status
244: of a keyboard LED (scroll lock, caps lock, etc). The problem is
245: generally intermittent and the keyboard can be "unlocked" by unplugging
246: and plugging it back in.
1.50 sthen 247: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/i386/pcvt.patch">
1.1 deraadt 248: A source code patch exists which remedies this problem.</a>
249: <p>
250: </ul>
1.31 henning 251: <a name="mac68k"></a>
252: <h3><font color="#e00000">mac68k</font></h3>
1.1 deraadt 253: <ul>
254: <li>No problems identified yet.
255: <p>
256: </ul>
1.31 henning 257: <a name="sparc"></a>
258: <h3><font color="#e00000">sparc</font></h3>
1.1 deraadt 259: <ul>
1.28 naddy 260: <li><font color="#009000"><strong>RELIABILITY FIX</strong></font><br>
1.1 deraadt 261: The 2.3 release does not run reliably on the sun4m LX/LC machines
262: (ie. Sparc Classic).
1.50 sthen 263: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/sparc/iommureg.patch">
1.1 deraadt 264: A source code patch exists which remedies this problem.</a>
265: Two kernels which replace the ones in the release are also provided:
1.50 sthen 266: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/sparc/bsd">bsd</a> and
267: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/sparc/bsd.scsi3">bsd.scsi3</a>.
1.1 deraadt 268: Other replacements for the 2.3 install tools are
1.50 sthen 269: <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/sparc">also available</a>.
1.1 deraadt 270: <p>
271: </ul>
1.31 henning 272: <a name="amiga"></a>
273: <h3><font color="#e00000">amiga</font></h3>
1.1 deraadt 274: <ul>
1.28 naddy 275: <li><font color="#009000"><strong>MINOR INCOMPATIBILITY</strong></font><br>
1.58 deraadt 276: The AmigaOS patch
1.1 deraadt 277: <a href="http://us.aminet.net/pub/aminet/util/sys/PoolMem.lha">PoolMem</a>
278: improves AmigaOS memory handling tremendously, but confuses loadbsd, which
279: grabs less memory from the system than is available. To work around the
280: problem, be sure to execute
281: <pre>
282: PoolMem remove
283: </pre>
284: right before running loadbsd. The next release of loadbsd will probably be
285: PoolMem-aware.
286: <p>
287: </ul>
1.31 henning 288: <a name="pmax"></a>
289: <h3><font color="#e00000">pmax</font></h3>
1.1 deraadt 290: <ul>
1.28 naddy 291: <li><font color="#009000"><strong>RELEASE WARNING</strong></font><br>
1.1 deraadt 292: The XFree86 binary set shipped on the CD and FTP site are not the
293: exact final set that we shipped for the other releases. A few minor
294: changes, mostly in <strong>xdm(1)</strong> configuration, were made
295: after those binaries were made. Patches for this might come out later.
296: <p>
1.28 naddy 297: <li><font color="#009000"><strong>X11 RELEASE ERROR</strong></font><br>
1.1 deraadt 298: The XFree86 binary set was linked with an older version of the C
299: library. To work around the problem, do the following as root.
300: <p>
1.31 henning 301: <pre>
302: cd /usr/lib/
303: ln -s libc.so.18.0 libc.so.17
304: </pre>
1.1 deraadt 305: <p>
1.28 naddy 306: <li><font color="#009000"><strong>X11 RELEASE ERROR</strong></font><br>
1.1 deraadt 307: The X11R5 server used in this port does not understand the default
308: authorization types used by the X11R6 clients, which results in no
309: clients being able to connect to the server. To fix this
310: problem add the line below to /usr/X11R6/lib/X11/xdm/xdm-config.
311: <p>
1.31 henning 312: <pre>
313: DisplayManager._0.authName: MIT-MAGIC-COOKIE-1
314: </pre>
1.1 deraadt 315: <p>
1.28 naddy 316: <li><font color="#009000"><strong>INSTALLATION PROCESS FLAW</strong></font><br>
1.1 deraadt 317: The pmax install does not correctly install the boot block.
318: To work around the problem, after the install program has finished, do
319: the following (assuming scsi id 0):
320: <p>
1.31 henning 321: <pre>
322: disklabel rz0 > /tmp/label
323: disklabel -R -B rz0 /tmp/label
324: </pre>
1.1 deraadt 325: <p>
326: </ul>
1.31 henning 327: <a name="arc"></a>
328: <h3><font color="#e00000">arc</font></h3>
1.1 deraadt 329: <ul>
1.28 naddy 330: <li><font color="#009000"><strong>RELEASE WARNING</strong></font><br>
1.1 deraadt 331: The XFree86 binary set shipped on the CD and FTP site are not the
332: exact final set that we shipped for the other releases. A few minor
333: changes, mostly in <strong>xdm(1)</strong> configuration, were made
334: after those binaries were made. Patches for this might come out later.
335: <p>
1.28 naddy 336: <li><font color="#009000"><strong>X11 RELEASE ERROR</strong></font><br>
1.1 deraadt 337: The XFree86 binary set was linked with an older version of the C
338: library. To work around the problem, do the following as root.
339: <p>
1.31 henning 340: <pre>
341: cd /usr/lib/
342: ln -s libc.so.18.0 libc.so.17
343: </pre>
1.1 deraadt 344: <p>
345: </ul>
1.31 henning 346: <a name="alpha"></a>
347: <h3><font color="#e00000">alpha</font></h3>
1.1 deraadt 348: <ul>
1.28 naddy 349: <li><font color="#009000"><strong>RELEASE WARNING</strong></font><br>
1.1 deraadt 350: When you start the install an upgrade option is advertised but
351: there really is no such option.
352: <p>
353: </ul>
1.31 henning 354: <a name="hp300"></a>
355: <h3><font color="#e00000">hp300</font></h3>
1.1 deraadt 356: <ul>
1.28 naddy 357: <li><font color="#009000"><strong>RELEASE WARNING</strong></font><br>
1.1 deraadt 358: When you start the install an upgrade option is advertised but
359: there really is no such option.
360: <p>
1.28 naddy 361: <li><font color="#009000"><strong>RELEASE WARNING</strong></font><br>
1.17 pvalchev 362: Unlabeled disks with weird geometries can panic the kernel.
1.1 deraadt 363: A fix will be made available when 2.3 is out.
364: <p>
365: </ul>
1.31 henning 366: <a name="mvme68k"></a>
367: <h3><font color="#e00000">mvme68k</font></h3>
1.1 deraadt 368: <ul>
369: <li>No problems identified yet.
370: <p>
371: </ul>
1.31 henning 372: <a name="powerpc"></a>
373: <h3><font color="#e00000">powerpc</font></h3>
1.1 deraadt 374: <ul>
1.28 naddy 375: <li><font color="#009000"><strong>SECURITY FIX</strong></font><br>
1.1 deraadt 376: The powerpc release shipped on the OpenBSD 2.3 CD does not contain
377: two late fixes applied late in the release cycle. The
1.58 deraadt 378: <a href="errata22.html#rmjob">rmjob</a> and
1.28 naddy 379: <a href="errata22.html#uucpd">uucpd</a> patches should be applied to
1.1 deraadt 380: the system if those subsystems are used.
381: <p>
1.59 deraadt 382:
1.1 deraadt 383: </ul>
384:
385: </body>
386: </html>
![[BACK]](/icons/back.gif){kind=icon}
Return to errata23.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www