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