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

Diff for /www/errata23.html between version 1.27 and 1.28

version 1.27, 2002/10/17 21:38:38 version 1.28, 2003/03/06 21:44:07
Line 1 
Line 1 
 <!DOCTYPE HTML PUBLIC  "-//IETF//DTD HTML Strict//EN">  <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
 <html>  <html>
 <head>  <head>
 <title>OpenBSD 2.3 errata</title>  <title>OpenBSD 2.3 errata</title>
 <link rev=made href=mailto:www@openbsd.org>  <link rev=made href="mailto:www@openbsd.org">
 <meta name="resource-type" content="document">  <meta name="resource-type" content="document">
 <meta name="description" content="the OpenBSD CD errata page">  <meta name="description" content="the OpenBSD CD errata page">
 <meta name="keywords" content="openbsd,cd,errata">  <meta name="keywords" content="openbsd,cd,errata">
Line 13 
Line 13 
 <BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#23238E">  <BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#23238E">
   
 <a href="index.html"><img alt="[OpenBSD]" height="30" width="141" src="images/smalltitle.gif" border="0"></a>  <a href="index.html"><img alt="[OpenBSD]" height="30" width="141" src="images/smalltitle.gif" border="0"></a>
 <h2><font color=#0000e0>  <h2><font color="#0000e0">
 This is the OpenBSD 2.3 release errata &amp; patch list:  This is the OpenBSD 2.3 release errata &amp; patch list:
   
 </font></h2>  </font></h2>
Line 36 
Line 36 
 <br>  <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.3.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 48 
Line 48 
   
 <dl>  <dl>
 <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=bootpd></a>  <a name=bootpd></a>
 <li><font color=#009000><strong>SECURITY FIX</strong></font><br>  <li><font color="#009000"><strong>SECURITY FIX</strong></font><br>
 A remotely exploitable problem exists in bootpd(8).  bootpd is disabled  A remotely exploitable problem exists in bootpd(8).  bootpd is disabled
 by default, but some people may actually be using it.  by default, but some people may actually be using it.
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/bootpd.patch>  <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/bootpd.patch">
 A source code patch exists which remedies this problem</a>, this is the  A source code patch exists which remedies this problem</a>, this is the
 second version of the patch.  second version of the patch.
 <p>  <p>
 <a name=tcpfix></a>  <a name=tcpfix></a>
 <li><font color=#009000><strong>SECURITY FIX</strong></font><br>  <li><font color="#009000"><strong>SECURITY FIX</strong></font><br>
 A remote machine lockup problem exists in the TCP decoding code.  A remote machine lockup problem exists in the TCP decoding code.
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/tcpfix.patch>  <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/tcpfix.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
 <a name=atapi></a>  <a name=atapi></a>
 <li><font color=#009000><strong>HARDWARE SUPPORT</strong></font><br>  <li><font color="#009000"><strong>HARDWARE SUPPORT</strong></font><br>
 Some ATAPI cdroms which do not support the full mandatory command set,  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.  (e.g. ATAPI_READ_CD_CAPACITY) do not work with the acd(4) driver.
 A patch is  A patch is
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/acd.patch>  <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/acd.patch">
 available here.</a>  available here.</a>
 <p>  <p>
 <a name=chpass></a>  <a name=chpass></a>
 <li><font color=#009000><strong>SECURITY FIX</strong></font><br>  <li><font color="#009000"><strong>SECURITY FIX</strong></font><br>
 Chpass(1) has a file descriptor leak which allows an  Chpass(1) has a file descriptor leak which allows an
 attacker to modify /etc/master.passwd.  attacker to modify /etc/master.passwd.
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/chpass.patch>  <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/chpass.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
 <a name=resid></a>  <a name=resid></a>
 <li><font color=#009000><strong>RELIABILITY FIX</strong></font><br>  <li><font color="#009000"><strong>RELIABILITY FIX</strong></font><br>
 Calling readv(2) with iov_len < 0 or > INT_MAX would result in a  Calling readv(2) with iov_len < 0 or > INT_MAX would result in a
 kernel panic.  This is the third revision of this patch.  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 href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/resid.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
 <a name=inetd></a>  <a name=inetd></a>
 <li><font color=#009000><strong>SECURITY FIX</strong></font><br>  <li><font color="#009000"><strong>SECURITY FIX</strong></font><br>
 Inetd had a file descriptor leak.  A patch is  Inetd had a file descriptor leak.  A patch is
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/inetd.patch>  <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/inetd.patch">
 available here.</a>  available here.</a>
 <p>  <p>
 <a name=unionfs></a>  <a name=unionfs></a>
 <li><font color=#009000><strong>BUG FIX</strong></font><br>  <li><font color="#009000"><strong>BUG FIX</strong></font><br>
 As shipped, unionfs had some serious problems.  As shipped, unionfs had some serious problems.
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/unionfs.patch>  <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/unionfs.patch">
 A patch is available to solve this</a>.  A patch is available to solve this</a>.
 <p>  <p>
 <a name=fdalloc></a>  <a name=fdalloc></a>
 <li><font color=#009000><strong>SECURITY FIX</strong></font><br>  <li><font color="#009000"><strong>SECURITY FIX</strong></font><br>
 Some non-allocated file descriptors have implied uses according to  Some non-allocated file descriptors have implied uses according to
 system libraries, and hence setuid and setgid processes should not  system libraries, and hence setuid and setgid processes should not
 be executed with these descriptors unallocated.  A patch which forces  be executed with these descriptors unallocated.  A patch which forces
 setuid and setgid processes to have some descriptors in fd slots  setuid and setgid processes to have some descriptors in fd slots
 0, 1, and 2 is  0, 1, and 2 is
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/fdalloc.patch>  <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/fdalloc.patch">
 available here.</a>  available here.</a>
 <p>  <p>
 <a name=resolver></a>  <a name=resolver></a>
 <li><font color=#009000><strong>SECURITY FIX</strong></font><br>  <li><font color="#009000"><strong>SECURITY FIX</strong></font><br>
 A benign looking buffer overflow in the resolver routines was re-introduced  A benign looking buffer overflow in the resolver routines was re-introduced
 accidentally.  The previously fixed behaviour is more correct.  A patch  accidentally.  The previously fixed behaviour is more correct.  A patch
 to fix this is  to fix this is
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/resolver.patch>  <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/resolver.patch">
 available here.</a>  available here.</a>
 <p>  <p>
 <a name=xlib></a>  <a name=xlib></a>
 <li><font color=#009000><strong>SECURITY FIX</strong></font><br>  <li><font color="#009000"><strong>SECURITY FIX</strong></font><br>
 Vulnerabilities have been found in the X11, Xt, Xaw and Xmu  Vulnerabilities have been found in the X11, Xt, Xaw and Xmu
 libraries. These affect xterm and all other setuid-root programs that  libraries. These affect xterm and all other setuid-root programs that
 use these libraries. The problems are associated with buffer overflows  use these libraries. The problems are associated with buffer overflows
Line 127 
Line 127 
 distributed with OpenBSD are vulnerable to some or all of these  distributed with OpenBSD are vulnerable to some or all of these
 problems.  problems.
 These problems are fixed in XFree86 patch 2.  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>  <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  The 2nd source patch</a> for these problems, specifically adapted to the
 OpenBSD 2.3 X11 tree, is available now.  OpenBSD 2.3 X11 tree, is available now.
 <p>  <p>
 <a name=kill></a>  <a name=kill></a>
 <li><font color=#009000><strong>SECURITY FIX</strong></font><br>  <li><font color="#009000"><strong>SECURITY FIX</strong></font><br>
 The kill(2) system call previously would permit a large set of signals to  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  be delivered to setuid or setgid processes.  If such processes were using
 those signals in dubious ways, this could have resulted in security  those signals in dubious ways, this could have resulted in security
 problems of various kinds.  problems of various kinds.
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/kill.patch>  <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  The fourth revision of a source code patch which solves the problem is
 available.</a>  available.</a>
 <p>  <p>
 <a name=immutable></a>  <a name=immutable></a>
 <li><font color=#009000><strong>SECURITY FIX</strong></font><br>  <li><font color="#009000"><strong>SECURITY FIX</strong></font><br>
 A possible new security problem exists if you rely on securelevels and  A possible new security problem exists if you rely on securelevels and
 immutable or append-only files or character devices.  The fix does not  immutable or append-only files or character devices.  The fix does not
 permit mmap'ing of immutable or append-only files which are otherwise  permit mmap'ing of immutable or append-only files which are otherwise
 writable, as the VM system will bypass the meaning of the file flags  writable, as the VM system will bypass the meaning of the file flags
 when writes happen to the file.  when writes happen to the file.
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/immutable.patch>  <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/immutable.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
 <a name=ipsec></a>  <a name=ipsec></a>
 <li><font color=#009000><strong>SECURITY FIX</strong></font><br>  <li><font color="#009000"><strong>SECURITY FIX</strong></font><br>
 If IPSEC communication is attempted by starting photurisd(8) (which is  If IPSEC communication is attempted by starting photurisd(8) (which is
 disabled by default), a system crash may be evoked from remote if  disabled by default), a system crash may be evoked from remote if
 an attacker uses some classes of invalid packets.  an attacker uses some classes of invalid packets.
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/ipsec.patch>  <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/ipsec.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
 <a name=xterm-xaw></a>  <a name=xterm-xaw></a>
 <li><font color=#009000><strong>SECURITY FIX</strong></font><br>  <li><font color="#009000"><strong>SECURITY FIX</strong></font><br>
 As stated in CERT advisory VB-98.04, there are buffer  As stated in CERT advisory VB-98.04, there are buffer
 overrun problems in <strong>xterm</strong> related to the input-Method,  overrun problems in <strong>xterm</strong> related to the input-Method,
 preeditType, and *Keymap resources. Additional buffer overruns exist in  preeditType, and *Keymap resources. Additional buffer overruns exist in
Line 171 
Line 171 
 a security vulnerability for any setuid-root program that uses the Xaw  a security vulnerability for any setuid-root program that uses the Xaw
 library (including xterm).  Patch1 from XFree86 3.3.2 corrects  library (including xterm).  Patch1 from XFree86 3.3.2 corrects
 these problems.  these problems.
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/xterm-xaw.patch>  <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 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  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  libraries on your system. These are expected to be extracted in
 <strong>/usr/X11R6</strong> using the command  <strong>/usr/X11R6</strong> using the command
 <strong>"tar xvfpz Xawfix.tgz"</strong>.  <strong>"tar xvfpz Xawfix.tgz"</strong>.
 The files are...  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/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/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/mac68k/Xawfix.tgz">mac68k</a>,
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/mvme68k/Xawfix.tgz>  <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/mvme68k/Xawfix.tgz">
         mvme68k</a>,          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/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/sparc/Xawfix.tgz">sparc</a>,
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/pmax/Xawfix.tgz>pmax</a>,  <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/pmax/Xawfix.tgz">pmax</a>,
 and  and
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/arc/Xawfix.tgz>arc</a>.  <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/arc/Xawfix.tgz">arc</a>.
 <p>  <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>  <a name=pctr></a>
 <li><font color=#009000><strong>RELIABILITY FIX</strong></font><br>  <li><font color="#009000"><strong>RELIABILITY FIX</strong></font><br>
 The pctr(4) driver has bugs that permit any user to crash the machine,  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  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  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.  the problem, recompile your kernel without the pctr(4) device driver.
 <p>  <p>
 <li><font color=#009000><strong>CORRUPTED FILE</strong></font><br>  <li><font color="#009000"><strong>CORRUPTED FILE</strong></font><br>
 The CD version of the precompiled ghostscript package is corrupted and  The CD version of the precompiled ghostscript package is corrupted and
 not installable.  The correct file can be retrieved by FTP from:  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>  <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>.  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  Its checksums (obtained with <i>cksum(1)</i>, <i>md5(1)</i> and
 <i>sha1(1)</i> respectively) are:  <i>sha1(1)</i> respectively) are:
Line 214 
Line 214 
 </ul>  </ul>
 <p>  <p>
 <a name=pcvt></a>  <a name=pcvt></a>
 <li><font color=#009000><strong>RELIABILITY FIX</strong></font><br>  <li><font color="#009000"><strong>RELIABILITY FIX</strong></font><br>
 The pcvt(4) console driver has a bug that can cause some keyboard  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  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  of a keyboard LED (scroll lock, caps lock, etc).  The problem is
 generally intermittent and the keyboard can be "unlocked" by unplugging  generally intermittent and the keyboard can be "unlocked" by unplugging
 and plugging it back in.  and plugging it back in.
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/i386/pcvt.patch>  <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/i386/pcvt.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
 </ul>  </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>  <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><font color="#009000"><strong>RELIABILITY FIX</strong></font><br>
 The 2.3 release does not run reliably on the sun4m LX/LC machines  The 2.3 release does not run reliably on the sun4m LX/LC machines
 (ie. Sparc Classic).  (ie. Sparc Classic).
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/sparc/iommureg.patch>  <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/sparc/iommureg.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 Two kernels which replace the ones in the release are also provided:  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">bsd</a> and
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/sparc/bsd.scsi3>bsd.scsi3</a>.  <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  Other replacements for the 2.3 install tools are
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/sparc>also available</a>.  <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.3/sparc">also available</a>.
 <p>  <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><font color="#009000"><strong>MINOR INCOMPATIBILITY</strong></font><br>
 The AmigaOS patch  The AmigaOS patch
 <a href="http://us.aminet.net/pub/aminet/util/sys/PoolMem.lha">PoolMem</a>  <a href="http://us.aminet.net/pub/aminet/util/sys/PoolMem.lha">PoolMem</a>
 improves AmigaOS memory handling tremendously, but confuses loadbsd, which  improves AmigaOS memory handling tremendously, but confuses loadbsd, which
Line 262 
Line 262 
 <p>  <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><font color="#009000"><strong>RELEASE WARNING</strong></font><br>
 The XFree86 binary set shipped on the CD and FTP site are not the  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  exact final set that we shipped for the other releases.  A few minor
 changes, mostly in <strong>xdm(1)</strong> configuration, were made  changes, mostly in <strong>xdm(1)</strong> configuration, were made
 after those binaries were made.  Patches for this might come out later.  after those binaries were made.  Patches for this might come out later.
 <p>  <p>
 <li><font color=#009000><strong>X11 RELEASE ERROR</strong></font><br>  <li><font color="#009000"><strong>X11 RELEASE ERROR</strong></font><br>
 The XFree86 binary set was linked with an older version of the C  The XFree86 binary set was linked with an older version of the C
 library.  To work around the problem, do the following as root.  library.  To work around the problem, do the following as root.
 <p>  <p>
Line 280 
Line 280 
 ln -s libc.so.18.0 libc.so.17  ln -s libc.so.18.0 libc.so.17
 </ul>  </ul>
 <p>  <p>
 <li><font color=#009000><strong>X11 RELEASE ERROR</strong></font><br>  <li><font color="#009000"><strong>X11 RELEASE ERROR</strong></font><br>
 The X11R5 server used in this port does not understand the default  The X11R5 server used in this port does not understand the default
 authorization types used by the X11R6 clients, which results in no  authorization types used by the X11R6 clients, which results in no
 clients being able to connect to the  server.  To fix this  clients being able to connect to the  server.  To fix this
Line 290 
Line 290 
 DisplayManager._0.authName: MIT-MAGIC-COOKIE-1  DisplayManager._0.authName: MIT-MAGIC-COOKIE-1
 </ul>  </ul>
 <p>  <p>
 <li><font color=#009000><strong>INSTALLATION PROCESS FLAW</strong></font><br>  <li><font color="#009000"><strong>INSTALLATION PROCESS FLAW</strong></font><br>
 The pmax install does not correctly install the boot block.  The pmax install does not correctly install the boot block.
 To work around the problem, after the install program has finished, do  To work around the problem, after the install program has finished, do
 the following (assuming scsi id 0):  the following (assuming scsi id 0):
Line 303 
Line 303 
 <p>  <p>
 </ul>  </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><font color="#009000"><strong>RELEASE WARNING</strong></font><br>
 The XFree86 binary set shipped on the CD and FTP site are not the  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  exact final set that we shipped for the other releases.  A few minor
 changes, mostly in <strong>xdm(1)</strong> configuration, were made  changes, mostly in <strong>xdm(1)</strong> configuration, were made
 after those binaries were made.  Patches for this might come out later.  after those binaries were made.  Patches for this might come out later.
 <p>  <p>
 <li><font color=#009000><strong>X11 RELEASE ERROR</strong></font><br>  <li><font color="#009000"><strong>X11 RELEASE ERROR</strong></font><br>
 The XFree86 binary set was linked with an older version of the C  The XFree86 binary set was linked with an older version of the C
 library.  To work around the problem, do the following as root.  library.  To work around the problem, do the following as root.
 <p>  <p>
Line 323 
Line 323 
 <p>  <p>
 </ul>  </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><font color="#009000"><strong>RELEASE WARNING</strong></font><br>
 When you start the install an upgrade option is advertised but  When you start the install an upgrade option is advertised but
 there really is no such option.  there really is no such option.
 <p>  <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><font color="#009000"><strong>RELEASE WARNING</strong></font><br>
 When you start the install an upgrade option is advertised but  When you start the install an upgrade option is advertised but
 there really is no such option.  there really is no such option.
 <p>  <p>
 <li><font color=#009000><strong>RELEASE WARNING</strong></font><br>  <li><font color="#009000"><strong>RELEASE WARNING</strong></font><br>
 Unlabeled disks with weird geometries can panic the kernel.  Unlabeled disks with weird geometries can panic the kernel.
 A fix will be made available when 2.3 is out.  A fix will be made available when 2.3 is out.
 <p>  <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>  <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><font color="#009000"><strong>SECURITY FIX</strong></font><br>
 The powerpc release shipped on the OpenBSD 2.3 CD does not contain  The powerpc release shipped on the OpenBSD 2.3 CD does not contain
 two late fixes applied late in the release cycle.  The  two late fixes applied late in the release cycle.  The
 <a href=errata22.html#rmjob>rmjob</a> and  <a href="errata22.html#rmjob">rmjob</a> and
 <a href=errata22.html#uucpd>uucpd</a> patches should be applied to  <a href="errata22.html#uucpd">uucpd</a> patches should be applied to
 the system if those subsystems are used.  the system if those subsystems are used.
 <p>  <p>
 </ul>  </ul>
Line 382 
Line 382 
   
 <hr>  <hr>
 <a href=index.html><img height=24 width=24 src=back.gif border=0 alt=OpenBSD></a>  <a href=index.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>
 <br><small>$OpenBSD$</small>  <br><small>$OpenBSD$</small>
   
 </body>  </body>
Legend:
Removed from v.1.27  
changed lines
  Added in v.1.28