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