===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/errata23.html,v
retrieving revision 1.66
retrieving revision 1.67
diff -c -r1.66 -r1.67
*** www/errata23.html	2014/10/02 14:34:45	1.66
--- www/errata23.html	2015/02/14 04:36:51	1.67
***************
*** 81,87 ****
  <hr>
  
  <ul>
! <li><a name="bootpd"></a>
  <font color="#009000"><strong>SECURITY FIX</strong></font>
  &nbsp; <i>All architectures</i><br>
  A remotely exploitable problem exists in bootpd(8).  bootpd is disabled
--- 81,87 ----
  <hr>
  
  <ul>
! <li id="bootpd">
  <font color="#009000"><strong>SECURITY FIX</strong></font>
  &nbsp; <i>All architectures</i><br>
  A remotely exploitable problem exists in bootpd(8).  bootpd is disabled
***************
*** 90,103 ****
  A source code patch exists which remedies this problem.</a>
  This is the second version of the patch.
  <p>
! <li><a name="tcpfix"></a>
  <font color="#009000"><strong>SECURITY FIX</strong></font>
  &nbsp; <i>All architectures</i><br>
  A remote machine lockup problem exists in the TCP decoding code.
  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/tcpfix.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
! <li><a name="atapi"></a>
  <font color="#009000"><strong>HARDWARE SUPPORT</strong></font>
  &nbsp; <i>All architectures</i><br>
  Some ATAPI cdroms which do not support the full mandatory command set,
--- 90,103 ----
  A source code patch exists which remedies this problem.</a>
  This is the second version of the patch.
  <p>
! <li id="tcpfix">
  <font color="#009000"><strong>SECURITY FIX</strong></font>
  &nbsp; <i>All architectures</i><br>
  A remote machine lockup problem exists in the TCP decoding code.
  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/tcpfix.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
! <li id="atapi">
  <font color="#009000"><strong>HARDWARE SUPPORT</strong></font>
  &nbsp; <i>All architectures</i><br>
  Some ATAPI cdroms which do not support the full mandatory command set,
***************
*** 106,112 ****
  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/acd.patch">
  available here.</a>
  <p>
! <li><a name="chpass"></a>
  <font color="#009000"><strong>SECURITY FIX</strong></font>
  &nbsp; <i>All architectures</i><br>
  Chpass(1) has a file descriptor leak which allows an
--- 106,112 ----
  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/acd.patch">
  available here.</a>
  <p>
! <li id="chpass">
  <font color="#009000"><strong>SECURITY FIX</strong></font>
  &nbsp; <i>All architectures</i><br>
  Chpass(1) has a file descriptor leak which allows an
***************
*** 114,120 ****
  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/chpass.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
! <li><a name="resid"></a>
  <font color="#009000"><strong>RELIABILITY FIX</strong></font>
  &nbsp; <i>All architectures</i><br>
  Calling readv(2) with iov_len &lt; 0 or &gt; INT_MAX would result in a
--- 114,120 ----
  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/chpass.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
! <li id="resid">
  <font color="#009000"><strong>RELIABILITY FIX</strong></font>
  &nbsp; <i>All architectures</i><br>
  Calling readv(2) with iov_len &lt; 0 or &gt; INT_MAX would result in a
***************
*** 122,142 ****
  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/resid.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
! <li><a name="inetd"></a>
  <font color="#009000"><strong>SECURITY FIX</strong></font>
  &nbsp; <i>All architectures</i><br>
  Inetd had a file descriptor leak.  A patch is
  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/inetd.patch">
  available here.</a>
  <p>
! <li><a name="unionfs"></a>
  <font color="#009000"><strong>BUG FIX</strong></font>
  &nbsp; <i>All architectures</i><br>
  As shipped, unionfs had some serious problems.
  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/unionfs.patch">
  A patch is available to solve this</a>.
  <p>
! <li><a name="fdalloc"></a>
  <font color="#009000"><strong>SECURITY FIX</strong></font>
  &nbsp; <i>All architectures</i><br>
  Some non-allocated file descriptors have implied uses according to
--- 122,142 ----
  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/resid.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
! <li id="inetd">
  <font color="#009000"><strong>SECURITY FIX</strong></font>
  &nbsp; <i>All architectures</i><br>
  Inetd had a file descriptor leak.  A patch is
  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/inetd.patch">
  available here.</a>
  <p>
! <li id="unionfs">
  <font color="#009000"><strong>BUG FIX</strong></font>
  &nbsp; <i>All architectures</i><br>
  As shipped, unionfs had some serious problems.
  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/unionfs.patch">
  A patch is available to solve this</a>.
  <p>
! <li id="fdalloc">
  <font color="#009000"><strong>SECURITY FIX</strong></font>
  &nbsp; <i>All architectures</i><br>
  Some non-allocated file descriptors have implied uses according to
***************
*** 147,153 ****
  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/fdalloc.patch">
  available here.</a>
  <p>
! <li><a name="resolver"></a>
  <font color="#009000"><strong>SECURITY FIX</strong></font>
  &nbsp; <i>All architectures</i><br>
  A benign looking buffer overflow in the resolver routines was re-introduced
--- 147,153 ----
  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/fdalloc.patch">
  available here.</a>
  <p>
! <li id="resolver">
  <font color="#009000"><strong>SECURITY FIX</strong></font>
  &nbsp; <i>All architectures</i><br>
  A benign looking buffer overflow in the resolver routines was re-introduced
***************
*** 156,162 ****
  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/resolver.patch">
  available here.</a>
  <p>
! <li><a name="xlib"></a>
  <font color="#009000"><strong>SECURITY FIX</strong></font>
  &nbsp; <i>All architectures</i><br>
  Vulnerabilities have been found in the X11, Xt, Xaw and Xmu
--- 156,162 ----
  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/resolver.patch">
  available here.</a>
  <p>
! <li id="xlib">
  <font color="#009000"><strong>SECURITY FIX</strong></font>
  &nbsp; <i>All architectures</i><br>
  Vulnerabilities have been found in the X11, Xt, Xaw and Xmu
***************
*** 172,178 ****
  The 2nd source patch</a> for these problems, specifically adapted to the
  OpenBSD 2.3 X11 tree, is available now.
  <p>
! <li><a name="kill"></a>
  <font color="#009000"><strong>SECURITY FIX</strong></font>
  &nbsp; <i>All architectures</i><br>
  The kill(2) system call previously would permit a large set of signals to
--- 172,178 ----
  The 2nd source patch</a> for these problems, specifically adapted to the
  OpenBSD 2.3 X11 tree, is available now.
  <p>
! <li id="kill">
  <font color="#009000"><strong>SECURITY FIX</strong></font>
  &nbsp; <i>All architectures</i><br>
  The kill(2) system call previously would permit a large set of signals to
***************
*** 183,189 ****
  The fourth revision of a source code patch which solves the problem is
  available.</a>
  <p>
! <li><a name="immutable"></a>
  <font color="#009000"><strong>SECURITY FIX</strong></font>
  &nbsp; <i>All architectures</i><br>
  A possible new security problem exists if you rely on securelevels and
--- 183,189 ----
  The fourth revision of a source code patch which solves the problem is
  available.</a>
  <p>
! <li id="immutable">
  <font color="#009000"><strong>SECURITY FIX</strong></font>
  &nbsp; <i>All architectures</i><br>
  A possible new security problem exists if you rely on securelevels and
***************
*** 194,200 ****
  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/immutable.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
! <li><a name="ipsec"></a>
  <font color="#009000"><strong>SECURITY FIX</strong></font>
  &nbsp; <i>All architectures</i><br>
  If IPSEC communication is attempted by starting photurisd(8) (which is
--- 194,200 ----
  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/immutable.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
! <li id="ipsec">
  <font color="#009000"><strong>SECURITY FIX</strong></font>
  &nbsp; <i>All architectures</i><br>
  If IPSEC communication is attempted by starting photurisd(8) (which is
***************
*** 203,210 ****
  <a href="http://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>
  &nbsp; <i>All architectures</i><br>
  As stated in CERT advisory VB-98.04, there are buffer
  overrun problems in <strong>xterm</strong> related to the input-Method,
--- 203,210 ----
  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/ipsec.patch">
  A source code patch exists which remedies this problem.</a>
  <p>
! <li id="xterm-xaw">
! <font color="#009000"><strong>SECURITY FIX</strong></font>
  &nbsp; <i>All architectures</i><br>
  As stated in CERT advisory VB-98.04, there are buffer
  overrun problems in <strong>xterm</strong> related to the input-Method,
***************
*** 234,240 ****
  and
  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/arc/Xawfix.tgz">arc</a>.
  <p>
! <li><a name="pctr"></a>
  <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
--- 234,240 ----
  and
  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/arc/Xawfix.tgz">arc</a>.
  <p>
! <li id="pctr">
  <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
***************
*** 254,261 ****
  <li>SHA1 (ghostscript-5.10.tgz) = bd9374fa547ac0078d5207463d3b0a19d80d213c
  </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
--- 254,261 ----
  <li>SHA1 (ghostscript-5.10.tgz) = bd9374fa547ac0078d5207463d3b0a19d80d213c
  </ul>
  <p>
! <li id="pcvt">
! <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