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