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