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