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