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