===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/errata23.html,v
retrieving revision 1.66
retrieving revision 1.67
diff -u -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,7 +81,7 @@
 <hr>
 
 <ul>
-<li><a name="bootpd"></a>
+<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,14 +90,14 @@
 A source code patch exists which remedies this problem.</a>
 This is the second version of the patch.
 <p>
-<li><a name="tcpfix"></a>
+<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><a name="atapi"></a>
+<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,7 +106,7 @@
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/acd.patch">
 available here.</a>
 <p>
-<li><a name="chpass"></a>
+<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,7 +114,7 @@
 <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>
+<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,21 +122,21 @@
 <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>
+<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><a name="unionfs"></a>
+<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><a name="fdalloc"></a>
+<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,7 +147,7 @@
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/fdalloc.patch">
 available here.</a>
 <p>
-<li><a name="resolver"></a>
+<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,7 +156,7 @@
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/common/resolver.patch">
 available here.</a>
 <p>
-<li><a name="xlib"></a>
+<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,7 +172,7 @@
 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>
+<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,7 +183,7 @@
 The fourth revision of a source code patch which solves the problem is
 available.</a>
 <p>
-<li><a name="immutable"></a>
+<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,7 +194,7 @@
 <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>
+<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,8 +203,8 @@
 <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>
+<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,7 +234,7 @@
 and
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.3/arc/Xawfix.tgz">arc</a>.
 <p>
-<li><a name="pctr"></a>
+<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,8 +254,8 @@
 <li>SHA1 (ghostscript-5.10.tgz) = bd9374fa547ac0078d5207463d3b0a19d80d213c
 </ul>
 <p>
-<a name="pcvt"></a>
-<li><font color="#009000"><strong>RELIABILITY FIX</strong></font><br>
+<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