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