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

Diff for /www/errata.html between version 1.143 and 1.144

version 1.143, 1998/09/15 16:18:55 version 1.144, 1998/11/10 19:12:16
Line 14 
Line 14 
   
 <img alt="[OpenBSD]" height=30 width=141 SRC="images/smalltitle.gif">  <img alt="[OpenBSD]" height=30 width=141 SRC="images/smalltitle.gif">
 <h2><font color=#0000e0>  <h2><font color=#0000e0>
 This is the OpenBSD 2.3 release errata & patch list:  This is the OpenBSD 2.4 release errata & patch list:
   
 </font></h2>  </font></h2>
   
 <hr>  <hr>
 <a href=errata21.html>For 2.1 errata, please refer here</a>.<br>  <a href=errata21.html>For 2.1 errata, please refer here</a>.<br>
 <a href=errata22.html>For 2.2 errata, please refer here</a>.<br>  <a href=errata22.html>For 2.2 errata, please refer here</a>.<br>
   <a href=errata23.html>For 2.3 errata, please refer here</a>.<br>
 <hr>  <hr>
   
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3.tar.gz>  <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.4.tar.gz>
 You can also fetch a tar.gz file containing all the following patches</a>.  You can also fetch a tar.gz file containing all the following patches</a>.
 This file is updated once a day.  This file is updated once a day.
   
Line 33 
Line 34 
 <a name=all></a>  <a name=all></a>
 <li><h3><font color=#e00000>All architectures</font></h3>  <li><h3><font color=#e00000>All architectures</font></h3>
 <ul>  <ul>
 <a name=atapi></a>  <li>No problems identified yet.
 <li><font color=#009000><strong>HARDWARE SUPPORT</strong></font><br>  
 Some ATAPI cdroms which do not support the full mandatory command set,  
 (e.g. ATAPI_READ_CD_CAPACITY) do not work with the acd(4) driver.  
 A patch is  
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/acd.patch>  
 available here.</a>  
 <p>  
 <a name=chpass></a>  
 <li><font color=#009000><strong>SECURITY FIX</strong></font><br>  
 Chpass(1) has a file descriptor leak which allows an  
 attacker to modify /etc/master.passwd.  
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/chpass.patch>  
 A source code patch exists which remedies this problem.</a>  
 <p>  
 <a name=resid></a>  
 <li><font color=#009000><strong>RELIABILITY FIX</strong></font><br>  
 Calling readv(2) with iov_len < 0 or > INT_MAX would result in a  
 kernel panic.  This is the third revision of this patch.  
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/resid.patch>  
 A source code patch exists which remedies this problem.</a>  
 <p>  
 <a name=inetd></a>  
 <li><font color=#009000><strong>SECURITY FIX</strong></font><br>  
 Inetd had a file descriptor leak.  A patch is  
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/inetd.patch>  
 available here.</a>  
 <p>  
 <a name=unionfs></a>  
 <li><font color=#009000><strong>BUG FIX</strong></font><br>  
 As shipped, unionfs had some serious problems.  
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/unionfs.patch>  
 A patch is available to solve this</a>.  
 <p>  
 <a name=fdalloc></a>  
 <li><font color=#009000><strong>SECURITY FIX</strong></font><br>  
 Some non-allocated file descriptors have implied uses according to  
 system libraries, and hence setuid and setgid processes should not  
 be executed with these descriptors unallocated.  A patch which forces  
 setuid and setgid processes to have some descriptors in fd slots  
 0, 1, and 2 is  
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/fdalloc.patch>  
 available here.</a>  
 <p>  
 <a name=xlib></a>  
 <li><font color=#009000><strong>SECURITY FIX</strong></font><br>  
 Vulnerabilities have been found in the X11, Xt, Xaw and Xmu  
 libraries. These affect xterm and all other setuid-root programs that  
 use these libraries. The problems are associated with buffer overflows  
 in code that processes user-supplied data. The Xt library problems  
 include those fixed in TOG's recent public patch 3 for X11R6.3. All  
 releases of XFree86 up to and including 3.3.2 patch 1 and the version  
 distributed with OpenBSD are vulnerable to some or all of these  
 problems.  
 These problems are fixed in XFree86 patch 2.  
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/XFree86-3.3.2.2.patch>  
 The 2nd source patch</a> for these problems, specifically adapted to the  
 OpenBSD 2.3 X11 tree, is available now.  
 <p>  
 <a name=kill></a>  
 <li><font color=#009000><strong>SECURITY FIX</strong></font><br>  
 The kill(2) system call previously would permit a large set of signals to  
 be delivered to setuid or setgid processes.  If such processes were using  
 those signals in dubious ways, this could have resulted in security  
 problems of various kinds.  
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/kill.patch>  
 The fourth revision of a source code patch which solves the problem is  
 available.</a>  
 <p>  
 <a name=immutable></a>  
 <li><font color=#009000><strong>SECURITY FIX</strong></font><br>  
 A possible new security problem exists if you rely on securelevels and  
 immutable or append-only files or character devices.  The fix does not  
 permit mmap'ing of immutable or append-only files which are otherwise  
 writeable, as the VM system will bypass the meaning of the file flags  
 when writes happen to the file.  
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/immutable.patch>  
 A source code patch exists which remedies this problem.</a>  
 <p>  
 <a name=ipsec></a>  
 <li><font color=#009000><strong>SECURITY FIX</strong></font><br>  
 If IPSEC communication is attempted by starting photurisd(8) (which is  
 disabled by default), a system crash may be evoked from remote if  
 an attacker uses some classes of invalid packets.  
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/ipsec.patch>  
 A source code patch exists which remedies this problem.</a>  
 <p>  
 <a name=xterm-xaw></a>  
 <li><font color=#009000><strong>SECURITY FIX</strong></font><br>  
 As stated in CERT advisory VB-98.04, there are buffer  
 overrun problems in <strong>xterm</strong> related to the input-Method,  
 preeditType, and *Keymap resources. Additional buffer overruns exist in  
 the <strong>Xaw</strong> library related to the inputMethod and  
 preeditType resources.   The xterm(1) problem represents a security  
 vulnerability for any platform where xterm is installed setuid-root  
 (as is the case for all OpenBSD platforms).  The Xaw problem represents  
 a security vulnerability for any setuid-root program that uses the Xaw  
 library (including xterm).  Patch1 from XFree86 3.3.2 corrects  
 these problems.  
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/xterm-xaw.patch>  
 We provide a version of this patch file specifically for the OpenBSD 2.3 tree</a>.  
 We also provide tar files which replace the xterm(1) binary and the libXaw  
 libraries on your system. These are expected to be extracted in  
 <strong>/usr/X11R6</strong> using the command  
 <strong>"tar xvfpz Xawfix.tgz"</strong>.  
 The files are...  
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/i386/Xawfix.tgz>i386</a>,  
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/alpha/Xawfix.tgz>alpha</a>,  
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/mac68k/Xawfix.tgz>mac68k</a>,  
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/mvme68k/Xawfix.tgz>  
         mvme68k</a>,  
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/hp300/Xawfix.tgz>hp300</a>,  
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/sparc/Xawfix.tgz>sparc</a>,  
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/pmax/Xawfix.tgz>pmax</a>,  
 and  
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/arc/Xawfix.tgz>arc</a>.  
 <p>  
 </ul>  </ul>
 <a name=i386></a>  <a name=i386></a>
 <li><h3><font color=#e00000>i386</font></h3>  <li><h3><font color=#e00000>i386</font></h3>
 <ul>  <ul>
 <a name=pctr></a>  <li>No problems identified yet.
 <li><font color=#009000><strong>RELIABILITY FIX</strong></font><br>  
 The pctr(4) driver has bugs that permit any user to crash the machine,  
 if the CPU is not an Intel CPU.  This problem has been properly fixed  
 since, but fixes are hard to apply to the 2.2 or 2.3 releases.  To avoid  
 the problem, recompile your kernel without the pctr(4) device driver.  
 <p>  
 <li><font color=#009000><strong>CORRUPTED FILE</strong></font><br>  
 The CD version of the precompiled ghostscript package is corrupted and  
 not installable.  The correct file can be retrieved by FTP from:  
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/2.3/packages/i386/ghostscript-5.10.tgz>  
 ftp://ftp.openbsd.org/pub/OpenBSD/2.3/packages/i386/ghostscript-5.10.tgz</a>.  
 Its checksums (obtained with <i>cksum(1)</i>, <i>md5(1)</i> and  
 <i>sha1(1)</i> respectively) are:  
 <ul>  
 <li>725752890 3639338 ghostscript-5.10.tgz  
 <li>MD5 (ghostscript-5.10.tgz) = 3144ca814ad1965d671be2b7be3d3050  
 <li>SHA1 (ghostscript-5.10.tgz) = bd9374fa547ac0078d5207463d3b0a19d80d213c  
 </ul>  </ul>
 <p>  
 <a name=pcvt></a>  
 <li><font color=#009000><strong>RELIABILITY FIX</strong></font><br>  
 The pcvt(4) console driver has a bug that can cause some keyboard  
 controllers to lock up when a key is pressed that toggles the status  
 of a keyboard LED (scroll lock, caps lock, etc).  The problem is  
 generally intermittent and the keyboard can be "unlocked" by unplugging  
 and plugging it back in.  
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/i386/pcvt.patch>  
 A source code patch exists which remedies this problem.</a>  
 <p>  
 </ul>  
 <a name=mac68k></a>  <a name=mac68k></a>
 <li><h3><font color=#e00000>mac68k</font></h3>  <li><h3><font color=#e00000>mac68k</font></h3>
 <ul>  <ul>
 <li>No problems identified yet.  <li>No problems identified yet.
 <p>  
 </ul>  </ul>
 <a name=sparc></a>  <a name=sparc></a>
 <li><h3><font color=#e00000>sparc</font></h3>  <li><h3><font color=#e00000>sparc</font></h3>
 <ul>  <ul>
 <li><font color=#009000><strong>RELIABILITY FIX</strong></font><br>  <li>No problems identified yet.
 The 2.3 release does not run reliably on the sun4m LX/LC machines  
 (ie. Sparc Classic).  
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/sparc/iommureg.patch>  
 A source code patch exists which remedies this problem.</a>  
 Two kernels which replace the ones in the release are also provided:  
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/sparc/bsd>bsd</a> and  
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/sparc/bsd.scsi3>bsd.scsi3</a>.  
 Other replacements for the 2.3 install tools are  
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/sparc>also available</a>.  
 <p>  
 </ul>  </ul>
 <a name=amiga></a>  <a name=amiga></a>
 <li><h3><font color=#e00000>amiga</font></h3>  <li><h3><font color=#e00000>amiga</font></h3>
 <ul>  <ul>
 <li><font color=#009000><strong>MINOR INCOMPATIBILITY</strong></font><br>  <li>No problems identified yet.
 The AmigaOS patch  
 <a href="http://us.aminet.net/pub/aminet/util/sys/PoolMem.lha">PoolMem</a>  
 improves AmigaOS memory handling tremendously, but confuses loadbsd, which  
 grabs less memory from the system than is available. To work around the  
 problem, be sure to execute  
 <pre>  
     PoolMem remove  
 </pre>  
 right before running loadbsd. The next release of loadbsd will probably be  
 PoolMem-aware.  
 <p>  
 </ul>  </ul>
 <a name=pmax></a>  <a name=pmax></a>
 <li><h3><font color=#e00000>pmax</font></h3>  <li><h3><font color=#e00000>pmax</font></h3>
 <ul>  <ul>
 <li><font color=#009000><strong>RELEASE WARNING</strong></font><br>  <li>No problems identified yet.
 The XFree86 binary set shipped on the CD and FTP site are not the  
 exact final set that we shipped for the other releases.  A few minor  
 changes, mostly in <strong>xdm(1)</strong> configuration, were made  
 after those binaries were made.  Patches for this might come out later.  
 <p>  
 <li><font color=#009000><strong>X11 RELEASE ERROR</strong></font><br>  
 The XFree86 binary set was linked with an older version of the C  
 library.  To work around the problem, do the following as root.  
 <p>  
 <ul>  
 cd /usr/lib/  
 <br>  
 ln -s libc.so.18.0 libc.so.17  
 </ul>  </ul>
 <p>  
 <li><font color=#009000><strong>X11 RELEASE ERROR</strong></font><br>  
 The X11R5 server used in this port does not understand the default  
 authorization types used by the X11R6 clients, which results in no  
 clients being able to connect to the  server.  To fix this  
 problem add the line below to /usr/X11R6/lib/X11/xdm/xdm-config.  
 <p>  
 <ul>  
 DisplayManager._0.authName: MIT-MAGIC-COOKIE-1  
 </ul>  
 <p>  
 <li><font color=#009000><strong>INSTALLATION PROCESS FLAW</strong></font><br>  
 The pmax install does not correctly install the boot block.  
 To work around the problem, after the install program has finished, do  
 the following (assuming scsi id 0):  
 <p>  
 <ul>  
 disklabel rz0 > /tmp/label  
 <br>  
 disklabel -R -B rz0 /tmp/label  
 </ul>  
 <p>  
 </ul>  
 <a name=arc></a>  <a name=arc></a>
 <li><h3><font color=#e00000>arc</font></h3>  <li><h3><font color=#e00000>arc</font></h3>
 <ul>  <ul>
 <li><font color=#009000><strong>RELEASE WARNING</strong></font><br>  <li>No problems identified yet.
 The XFree86 binary set shipped on the CD and FTP site are not the  
 exact final set that we shipped for the other releases.  A few minor  
 changes, mostly in <strong>xdm(1)</strong> configuration, were made  
 after those binaries were made.  Patches for this might come out later.  
 <p>  
 <li><font color=#009000><strong>X11 RELEASE ERROR</strong></font><br>  
 The XFree86 binary set was linked with an older version of the C  
 library.  To work around the problem, do the following as root.  
 <p>  
 <ul>  
 cd /usr/lib/  
 <br>  
 ln -s libc.so.18.0 libc.so.17  
 </ul>  </ul>
 <p>  
 </ul>  
 <a name=alpha></a>  <a name=alpha></a>
 <li><h3><font color=#e00000>alpha</font></h3>  <li><h3><font color=#e00000>alpha</font></h3>
 <ul>  <ul>
 <li><font color=#009000><strong>RELEASE WARNING</strong></font><br>  <li>No problems identified yet.
 When you start the install an upgrade option is advertised but  
 there really is no such option.  
 <p>  
 </ul>  </ul>
 <a name=hp300></a>  <a name=hp300></a>
 <li><h3><font color=#e00000>hp300</font></h3>  <li><h3><font color=#e00000>hp300</font></h3>
 <ul>  <ul>
 <li><font color=#009000><strong>RELEASE WARNING</strong></font><br>  <li>No problems identified yet.
 When you start the install an upgrade option is advertised but  
 there really is no such option.  
 <p>  
 <li><font color=#009000><strong>RELEASE WARNING</strong></font><br>  
 Unlabelled disks with weird geometries can panic the kernel.  
 A fix will be made available when 2.3 is out.  
 <p>  
 </ul>  </ul>
 <a name=mvme68k></a>  <a name=mvme68k></a>
 <li><h3><font color=#e00000>mvme68k</font></h3>  <li><h3><font color=#e00000>mvme68k</font></h3>
 <ul>  <ul>
 <li>No problems identified yet.  <li>No problems identified yet.
 <p>  
 </ul>  </ul>
 <a name=powerpc></a>  <a name=powerpc></a>
 <li><h3><font color=#e00000>powerpc</font></h3>  <li><h3><font color=#e00000>powerpc</font></h3>
 <ul>  <ul>
 <li><font color=#009000><strong>SECURITY FIX</strong></font><br>  <li>No problems identified yet.
 The powerpc release shipped on the OpenBSD 2.3 CD does not contain  </ul>
 two late fixes applied late in the release cycle.  The  
 <a href=errata22.html#rmjob>rmjob</a> and  
 <a href=errata22.html#uucpd>uucpd</a> patches should be applied to  
 the system if those subsystems are used.  
 <p>  <p>
 </ul>  </ul>
 </ul>  
 <br>  <br>
   
 <hr>  <hr>
 <a href=errata21.html>For 2.1 errata, please refer here</a>.<br>  <a href=errata21.html>For 2.1 errata, please refer here</a>.<br>
 <a href=errata22.html>For 2.2 errata, please refer here</a>.<br>  <a href=errata22.html>For 2.2 errata, please refer here</a>.<br>
   <a href=errata23.html>For 2.3 errata, please refer here</a>.<br>
 <hr>  <hr>
 <a href=orders.html><img height=24 width=24 src=back.gif border=0 alt=OpenBSD></a>  <a href=orders.html><img height=24 width=24 src=back.gif border=0 alt=OpenBSD></a>
 <a href=mailto:www@openbsd.org>www@openbsd.org</a>  <a href=mailto:www@openbsd.org>www@openbsd.org</a>
Legend:
Removed from v.1.143  
changed lines
  Added in v.1.144