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