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