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

Annotation of www/errata23.html, Revision 1.12

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