[BACK]Return to errata23.html CVS log [TXT][DIR] Up to [local] / www

Annotation of www/errata23.html, Revision 1.11

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