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