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