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