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