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