Annotation of www/errata.html, Revision 1.143
1.1 deraadt 1: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML Strict//EN">
2: <html>
3: <head>
1.64 deraadt 4: <title>OpenBSD release errata</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="the OpenBSD CD errata page">
8: <meta name="keywords" content="openbsd,cd,errata">
9: <meta name="distribution" content="global">
1.107 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">
14:
1.127 pauls 15: <img alt="[OpenBSD]" height=30 width=141 SRC="images/smalltitle.gif">
1.68 deraadt 16: <h2><font color=#0000e0>
1.93 deraadt 17: This is the OpenBSD 2.3 release errata & patch list:
1.94 deraadt 18:
1.96 deraadt 19: </font></h2>
20:
1.94 deraadt 21: <hr>
22: <a href=errata21.html>For 2.1 errata, please refer here</a>.<br>
23: <a href=errata22.html>For 2.2 errata, please refer here</a>.<br>
24: <hr>
25:
1.142 deraadt 26: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3.tar.gz>
27: You can also fetch a tar.gz file containing all the following patches</a>.
28: This file is updated once a day.
29:
30: <hr>
31:
1.25 deraadt 32: <ul>
1.43 deraadt 33: <a name=all></a>
1.67 deraadt 34: <li><h3><font color=#e00000>All architectures</font></h3>
1.25 deraadt 35: <ul>
1.141 deraadt 36: <a name=atapi></a>
37: <li><font color=#009000><strong>HARDWARE SUPPORT</strong></font><br>
38: Some ATAPI cdroms which do not support the full mandatory command set,
39: (e.g. ATAPI_READ_CD_CAPACITY) do not work with the acd(4) driver.
40: A patch is
41: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/acd.patch>
42: available here.</a>
43: <p>
1.140 millert 44: <a name=chpass></a>
45: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
46: Chpass(1) has a file descriptor leak which allows an
47: attacker to modify /etc/master.passwd.
48: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/chpass.patch>
49: A source code patch exists which remedies this problem.</a>
50: <p>
1.138 deraadt 51: <a name=resid></a>
52: <li><font color=#009000><strong>RELIABILITY FIX</strong></font><br>
53: Calling readv(2) with iov_len < 0 or > INT_MAX would result in a
1.139 millert 54: kernel panic. This is the third revision of this patch.
1.138 deraadt 55: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/resid.patch>
56: A source code patch exists which remedies this problem.</a>
57: <p>
58: <a name=inetd></a>
1.135 deraadt 59: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
60: Inetd had a file descriptor leak. A patch is
61: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/inetd.patch>
62: available here.</a>
63: <p>
1.133 deraadt 64: <a name=unionfs></a>
65: <li><font color=#009000><strong>BUG FIX</strong></font><br>
66: As shipped, unionfs had some serious problems.
67: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/unionfs.patch>
68: A patch is available to solve this</a>.
69: <p>
1.131 deraadt 70: <a name=fdalloc></a>
71: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
72: Some non-allocated file descriptors have implied uses according to
73: system libraries, and hence setuid and setgid processes should not
74: be executed with these descriptors unallocated. A patch which forces
75: setuid and setgid processes to have some descriptors in fd slots
76: 0, 1, and 2 is
1.132 deraadt 77: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/fdalloc.patch>
1.131 deraadt 78: available here.</a>
79: <p>
1.120 matthieu 80: <a name=xlib></a>
81: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
82: Vulnerabilities have been found in the X11, Xt, Xaw and Xmu
83: libraries. These affect xterm and all other setuid-root programs that
84: use these libraries. The problems are associated with buffer overflows
85: in code that processes user-supplied data. The Xt library problems
86: include those fixed in TOG's recent public patch 3 for X11R6.3. All
87: releases of XFree86 up to and including 3.3.2 patch 1 and the version
88: distributed with OpenBSD are vulnerable to some or all of these
89: problems.
1.121 deraadt 90: These problems are fixed in XFree86 patch 2.
91: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/XFree86-3.3.2.2.patch>
1.143 ! deraadt 92: The 2nd source patch</a> for these problems, specifically adapted to the
1.121 deraadt 93: OpenBSD 2.3 X11 tree, is available now.
1.120 matthieu 94: <p>
1.116 deraadt 95: <a name=kill></a>
96: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
97: The kill(2) system call previously would permit a large set of signals to
98: be delivered to setuid or setgid processes. If such processes were using
99: those signals in dubious ways, this could have resulted in security
100: problems of various kinds.
101: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/kill.patch>
1.125 deraadt 102: The fourth revision of a source code patch which solves the problem is
1.117 deraadt 103: available.</a>
1.116 deraadt 104: <p>
1.108 deraadt 105: <a name=immutable></a>
106: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
1.109 deraadt 107: A possible new security problem exists if you rely on securelevels and
108: immutable or append-only files or character devices. The fix does not
109: permit mmap'ing of immutable or append-only files which are otherwise
110: writeable, as the VM system will bypass the meaning of the file flags
111: when writes happen to the file.
1.108 deraadt 112: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/immutable.patch>
113: A source code patch exists which remedies this problem.</a>
114: <p>
1.102 deraadt 115: <a name=ipsec></a>
116: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
117: If IPSEC communication is attempted by starting photurisd(8) (which is
1.103 deraadt 118: disabled by default), a system crash may be evoked from remote if
119: an attacker uses some classes of invalid packets.
1.102 deraadt 120: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/ipsec.patch>
121: A source code patch exists which remedies this problem.</a>
1.106 deraadt 122: <p>
1.99 matthieu 123: <a name=xterm-xaw></a>
124: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
125: As stated in CERT advisory VB-98.04, there are buffer
1.103 deraadt 126: overrun problems in <strong>xterm</strong> related to the input-Method,
127: preeditType, and *Keymap resources. Additional buffer overruns exist in
128: the <strong>Xaw</strong> library related to the inputMethod and
129: preeditType resources. The xterm(1) problem represents a security
130: vulnerability for any platform where xterm is installed setuid-root
131: (as is the case for all OpenBSD platforms). The Xaw problem represents
132: a security vulnerability for any setuid-root program that uses the Xaw
133: library (including xterm). Patch1 from XFree86 3.3.2 corrects
134: these problems.
1.99 matthieu 135: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/xterm-xaw.patch>
1.101 deraadt 136: We provide a version of this patch file specifically for the OpenBSD 2.3 tree</a>.
1.107 deraadt 137: We also provide tar files which replace the xterm(1) binary and the libXaw
138: libraries on your system. These are expected to be extracted in
139: <strong>/usr/X11R6</strong> using the command
140: <strong>"tar xvfpz Xawfix.tgz"</strong>.
141: The files are...
1.118 deraadt 142: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/i386/Xawfix.tgz>i386</a>,
143: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/alpha/Xawfix.tgz>alpha</a>,
144: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/mac68k/Xawfix.tgz>mac68k</a>,
145: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/mvme68k/Xawfix.tgz>
1.105 deraadt 146: mvme68k</a>,
1.118 deraadt 147: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/hp300/Xawfix.tgz>hp300</a>,
148: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/sparc/Xawfix.tgz>sparc</a>,
149: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/pmax/Xawfix.tgz>pmax</a>,
1.105 deraadt 150: and
1.118 deraadt 151: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/arc/Xawfix.tgz>arc</a>.
1.86 millert 152: <p>
1.25 deraadt 153: </ul>
1.42 deraadt 154: <a name=i386></a>
1.67 deraadt 155: <li><h3><font color=#e00000>i386</font></h3>
1.25 deraadt 156: <ul>
1.124 deraadt 157: <a name=pctr></a>
158: <li><font color=#009000><strong>RELIABILITY FIX</strong></font><br>
159: The pctr(4) driver has bugs that permit any user to crash the machine,
160: if the CPU is not an Intel CPU. This problem has been properly fixed
161: since, but fixes are hard to apply to the 2.2 or 2.3 releases. To avoid
162: the problem, recompile your kernel without the pctr(4) device driver.
163: <p>
1.104 niklas 164: <li><font color=#009000><strong>CORRUPTED FILE</strong></font><br>
165: The CD version of the precompiled ghostscript package is corrupted and
166: not installable. The correct file can be retrieved by FTP from:
1.107 deraadt 167: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/2.3/packages/i386/ghostscript-5.10.tgz>
1.104 niklas 168: ftp://ftp.openbsd.org/pub/OpenBSD/2.3/packages/i386/ghostscript-5.10.tgz</a>.
169: Its checksums (obtained with <i>cksum(1)</i>, <i>md5(1)</i> and
170: <i>sha1(1)</i> respectively) are:
171: <ul>
172: <li>725752890 3639338 ghostscript-5.10.tgz
173: <li>MD5 (ghostscript-5.10.tgz) = 3144ca814ad1965d671be2b7be3d3050
174: <li>SHA1 (ghostscript-5.10.tgz) = bd9374fa547ac0078d5207463d3b0a19d80d213c
175: </ul>
1.39 deraadt 176: <p>
1.130 millert 177: <a name=pcvt></a>
178: <li><font color=#009000><strong>RELIABILITY FIX</strong></font><br>
179: The pcvt(4) console driver has a bug that can cause some keyboard
180: controllers to lock up when a key is pressed that toggles the status
181: of a keyboard LED (scroll lock, caps lock, etc). The problem is
182: generally intermittent and the keyboard can be "unlocked" by unplugging
183: and plugging it back in.
184: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/i386/pcvt.patch>
185: A source code patch exists which remedies this problem.</a>
186: <p>
1.39 deraadt 187: </ul>
1.47 deraadt 188: <a name=mac68k></a>
1.67 deraadt 189: <li><h3><font color=#e00000>mac68k</font></h3>
1.39 deraadt 190: <ul>
1.93 deraadt 191: <li>No problems identified yet.
1.70 gene 192: <p>
1.25 deraadt 193: </ul>
1.65 deraadt 194: <a name=sparc></a>
1.67 deraadt 195: <li><h3><font color=#e00000>sparc</font></h3>
1.25 deraadt 196: <ul>
1.100 deraadt 197: <li><font color=#009000><strong>RELIABILITY FIX</strong></font><br>
198: The 2.3 release does not run reliably on the sun4m LX/LC machines
1.98 deraadt 199: (ie. Sparc Classic).
200: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/sparc/iommureg.patch>
201: A source code patch exists which remedies this problem.</a>
1.115 deraadt 202: Two kernels which replace the ones in the release are also provided:
203: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/sparc/bsd>bsd</a> and
204: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/sparc/bsd.scsi3>bsd.scsi3</a>.
1.123 deraadt 205: Other replacements for the 2.3 install tools are
206: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/sparc>also available</a>.
1.63 marc 207: <p>
1.39 deraadt 208: </ul>
1.93 deraadt 209: <a name=amiga></a>
1.67 deraadt 210: <li><h3><font color=#e00000>amiga</font></h3>
1.93 deraadt 211: <ul>
1.134 espie 212: <li><font color=#009000><strong>MINOR INCOMPATIBILITY</strong></font><br>
213: The AmigaOS patch
214: <a href="http://us.aminet.net/pub/aminet/util/sys/PoolMem.lha">PoolMem</a>
215: improves AmigaOS memory handling tremendously, but confuses loadbsd, which
216: grabs less memory from the system than is available. To work around the
217: problem, be sure to execute
218: <pre>
219: PoolMem remove
220: </pre>
221: right before running loadbsd. The next release of loadbsd will probably be
222: PoolMem-aware.
1.39 deraadt 223: <p>
1.25 deraadt 224: </ul>
1.65 deraadt 225: <a name=pmax></a>
1.67 deraadt 226: <li><h3><font color=#e00000>pmax</font></h3>
1.25 deraadt 227: <ul>
1.100 deraadt 228: <li><font color=#009000><strong>RELEASE WARNING</strong></font><br>
229: The XFree86 binary set shipped on the CD and FTP site are not the
1.97 deraadt 230: exact final set that we shipped for the other releases. A few minor
231: changes, mostly in <strong>xdm(1)</strong> configuration, were made
232: after those binaries were made. Patches for this might come out later.
1.39 deraadt 233: <p>
1.112 deraadt 234: <li><font color=#009000><strong>X11 RELEASE ERROR</strong></font><br>
1.119 ryker 235: The XFree86 binary set was linked with an older version of the C
1.113 deraadt 236: library. To work around the problem, do the following as root.
237: <p>
1.110 millert 238: <ul>
239: cd /usr/lib/
240: <br>
241: ln -s libc.so.18.0 libc.so.17
242: </ul>
243: <p>
1.129 jason 244: <li><font color=#009000><strong>X11 RELEASE ERROR</strong></font><br>
245: The X11R5 server used in this port does not understand the default
246: authorization types used by the X11R6 clients, which results in no
247: clients being able to connect to the server. To fix this
248: problem add the line below to /usr/X11R6/lib/X11/xdm/xdm-config.
249: <p>
250: <ul>
251: DisplayManager._0.authName: MIT-MAGIC-COOKIE-1
252: </ul>
253: <p>
1.112 deraadt 254: <li><font color=#009000><strong>INSTALLATION PROCESS FLAW</strong></font><br>
1.110 millert 255: The pmax install does not correctly install the boot block.
256: To work around the problem, after the install program has finished, do
257: the following (assuming scsi id 0):
1.113 deraadt 258: <p>
1.110 millert 259: <ul>
1.114 millert 260: disklabel rz0 > /tmp/label
1.110 millert 261: <br>
1.114 millert 262: disklabel -R -B rz0 /tmp/label
1.110 millert 263: </ul>
264: <p>
1.25 deraadt 265: </ul>
1.65 deraadt 266: <a name=arc></a>
1.67 deraadt 267: <li><h3><font color=#e00000>arc</font></h3>
1.59 deraadt 268: <ul>
1.100 deraadt 269: <li><font color=#009000><strong>RELEASE WARNING</strong></font><br>
270: The XFree86 binary set shipped on the CD and FTP site are not the
1.97 deraadt 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.
1.69 deraadt 274: <p>
1.112 deraadt 275: <li><font color=#009000><strong>X11 RELEASE ERROR</strong></font><br>
1.119 ryker 276: The XFree86 binary set was linked with an older version of the C
1.113 deraadt 277: library. To work around the problem, do the following as root.
278: <p>
1.111 deraadt 279: <ul>
280: cd /usr/lib/
281: <br>
282: ln -s libc.so.18.0 libc.so.17
283: </ul>
284: <p>
1.59 deraadt 285: </ul>
1.93 deraadt 286: <a name=alpha></a>
1.67 deraadt 287: <li><h3><font color=#e00000>alpha</font></h3>
1.56 deraadt 288: <ul>
1.110 millert 289: <li><font color=#009000><strong>RELEASE WARNING</strong></font><br>
290: When you start the install an upgrade option is advertised but
291: there really is no such option.
1.56 deraadt 292: <p>
293: </ul>
1.93 deraadt 294: <a name=hp300></a>
1.67 deraadt 295: <li><h3><font color=#e00000>hp300</font></h3>
1.110 millert 296: <ul>
297: <li><font color=#009000><strong>RELEASE WARNING</strong></font><br>
298: When you start the install an upgrade option is advertised but
299: there really is no such option.
1.56 deraadt 300: <p>
1.110 millert 301: <li><font color=#009000><strong>RELEASE WARNING</strong></font><br>
302: Unlabelled disks with weird geometries can panic the kernel.
303: A fix will be made available when 2.3 is out.
1.56 deraadt 304: <p>
305: </ul>
1.93 deraadt 306: <a name=mvme68k></a>
1.67 deraadt 307: <li><h3><font color=#e00000>mvme68k</font></h3>
1.25 deraadt 308: <ul>
1.39 deraadt 309: <li>No problems identified yet.
310: <p>
1.25 deraadt 311: </ul>
1.95 deraadt 312: <a name=powerpc></a>
313: <li><h3><font color=#e00000>powerpc</font></h3>
314: <ul>
315: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
316: The powerpc release shipped on the OpenBSD 2.3 CD does not contain
317: two late fixes applied late in the release cycle. The
318: <a href=errata22.html#rmjob>rmjob</a> and
319: <a href=errata22.html#uucpd>uucpd</a> patches should be applied to
320: the system if those subsystems are used.
321: <p>
322: </ul>
1.25 deraadt 323: </ul>
324: <br>
1.75 deraadt 325:
1.25 deraadt 326: <hr>
1.93 deraadt 327: <a href=errata21.html>For 2.1 errata, please refer here</a>.<br>
328: <a href=errata22.html>For 2.2 errata, please refer here</a>.<br>
1.2 deraadt 329: <hr>
1.127 pauls 330: <a href=orders.html><img height=24 width=24 src=back.gif border=0 alt=OpenBSD></a>
1.2 deraadt 331: <a href=mailto:www@openbsd.org>www@openbsd.org</a>
1.143 ! deraadt 332: <br><small>$OpenBSD: errata.html,v 1.142 1998/08/05 08:26:33 deraadt Exp $</small>
1.2 deraadt 333:
334: </body>
335: </html>
![[BACK]](/icons/back.gif){kind=icon}
Return to errata.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www