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