===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/errata43.html,v
retrieving revision 1.40
retrieving revision 1.41
diff -u -r1.40 -r1.41
--- www/errata43.html	2014/03/31 03:12:47	1.40
+++ www/errata43.html	2014/03/31 16:02:48	1.41
@@ -78,7 +78,8 @@
 <ul>
 
 <li><a name="013_pf"></a>
-<font color="#009000"><strong>013: RELIABILITY FIX: April 11, 2009</strong></font> &nbsp; <i>All architectures</i><br>
+<font color="#009000"><strong>013: RELIABILITY FIX: April 11, 2009</strong></font>
+&nbsp; <i>All architectures</i><br>
 When pf attempts to perform translation on a specially crafted IP datagram,
 a null pointer dereference will occur, resulting in a kernel panic.
 In certain configurations this may be triggered by a remote attacker.
@@ -98,7 +99,8 @@
 <p>
 
 <li><a name="012_openssl"></a>
-<font color="#009000"><strong>012: RELIABILITY FIX: April 8, 2009</strong></font> &nbsp; <i>All architectures</i><br>
+<font color="#009000"><strong>012: RELIABILITY FIX: April 8, 2009</strong></font>
+&nbsp; <i>All architectures</i><br>
 The OpenSSL ASN.1 handling code could be forced to perform invalid memory
 accesses through the use of certain invalid strings
 (<a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0590">CVE-2009-0590</a>)
@@ -115,7 +117,8 @@
 <p>
 
 <li><a name="011_sudo"></a>
-<font color="#009000"><strong>011: SECURITY FIX: February 22, 2009</strong></font> &nbsp; <i>All architectures</i><br>
+<font color="#009000"><strong>011: SECURITY FIX: February 22, 2009</strong></font>
+&nbsp; <i>All architectures</i><br>
 sudo(8) may allow a user listed in the sudoers file to run a command
 as a different user than their access rule specifies when a Unix
 group is used in the RunAs portion of the rule.  The bug only manifests
@@ -127,7 +130,8 @@
 <p>
 
 <li><a name="010_bgpd"></a>
-<font color="#009000"><strong>010: RELIABILITY FIX: February 18, 2009</strong></font> &nbsp; <i>All architectures</i><br>
+<font color="#009000"><strong>010: RELIABILITY FIX: February 18, 2009</strong></font>
+&nbsp; <i>All architectures</i><br>
 bgpd(8) did not correctly prepend its own AS to very long AS paths, causing
 the process to terminate because of the resulting corrupt path.
 <br>
@@ -136,7 +140,8 @@
 <p>
 
 <li><a name="009_bgpd"></a>
-<font color="#009000"><strong>009: RELIABILITY FIX: January 30, 2009</strong></font> &nbsp; <i>All architectures</i><br>
+<font color="#009000"><strong>009: RELIABILITY FIX: January 30, 2009</strong></font>
+&nbsp; <i>All architectures</i><br>
 Upon reception of an invalid update with 4-byte AS attributes, bgpd -
 adhering to the RFCs - closed the session to the neighbor.
 This error in the specification allowed 3rd parties to close remote BGP
@@ -148,7 +153,8 @@
 <p>
 
 <li><a name="008_bind"></a>
-<font color="#009000"><strong>008: SECURITY FIX: January 14, 2009</strong></font> &nbsp; <i>All architectures</i><br>
+<font color="#009000"><strong>008: SECURITY FIX: January 14, 2009</strong></font>
+&nbsp; <i>All architectures</i><br>
 named(8) did not correctly check the return value of a DSA verification
 function, potentially allowing bypass of verification of DNSSEC DSA
 signatures.
@@ -159,7 +165,8 @@
 <p>
 
 <li><a name="007_openssl"></a>
-<font color="#009000"><strong>007: SECURITY FIX: January 9, 2009</strong></font> &nbsp; <i>All architectures</i><br>
+<font color="#009000"><strong>007: SECURITY FIX: January 9, 2009</strong></font>
+&nbsp; <i>All architectures</i><br>
 The OpenSSL libraries did not correctly check the return value from
 certain verification functions, allowing validation to be bypassed and
 permitting a remote attacker to conduct a "man in the middle attack"
@@ -172,7 +179,8 @@
 <p>
 
 <li><a name="006_ndp"></a>
-<font color="#009000"><strong>006: SECURITY FIX: October 2, 2008</strong></font> &nbsp; <i>All architectures</i><br>
+<font color="#009000"><strong>006: SECURITY FIX: October 2, 2008</strong></font>
+&nbsp; <i>All architectures</i><br>
 The Neighbor Discovery Protocol (ndp) did not correctly verify neighbor
 solicitation requests maybe allowing a nearby attacker to intercept traffic.
 The attacker must have IPv6 connectivity to the same router as their target for
@@ -184,7 +192,8 @@
 <p>
 
 <li><a name="005_pcb"></a>
-<font color="#009000"><strong>005: RELIABILITY FIX: July 29, 2008</strong></font> &nbsp; <i>All architectures</i><br>
+<font color="#009000"><strong>005: RELIABILITY FIX: July 29, 2008</strong></font>
+&nbsp; <i>All architectures</i><br>
 Some kinds of IPv6 usage would leak kernel memory (in particular, this path
 was exercised by the named(8) patch for port randomization).  Since INET6 is
 enabled by default, this condition affects all systems.
@@ -194,7 +203,8 @@
 <p>
 
 <li><a name="004_bind"></a>
-<font color="#009000"><strong>004: SECURITY FIX: July 23, 2008</strong></font> &nbsp; <i>All architectures</i><br>
+<font color="#009000"><strong>004: SECURITY FIX: July 23, 2008</strong></font>
+&nbsp; <i>All architectures</i><br>
 <strong>2nd revision, July 23, 2008</strong><br>
 A vulnerability has been found with BIND. An attacker could use this vulnerability
 to poison the cache of a recursive resolving name server.
@@ -205,7 +215,8 @@
 <p>
 
 <li><a name="003_xorg"></a>
-<font color="#009000"><strong>003: SECURITY FIX: July 15, 2008</strong></font> &nbsp; <i>All architectures</i><br>
+<font color="#009000"><strong>003: SECURITY FIX: July 15, 2008</strong></font>
+&nbsp; <i>All architectures</i><br>
 Multiple vulnerabilities have been discovered in X.Org.<br>
 RENDER Extension heap buffer overflow,
 RENDER Extension crash,
@@ -223,7 +234,8 @@
 <p>
 
 <li><a name="002_openssh2"></a>
-<font color="#009000"><strong>002: SECURITY FIX: April 3, 2008</strong></font> &nbsp; <i>All architectures</i><br>
+<font color="#009000"><strong>002: SECURITY FIX: April 3, 2008</strong></font>
+&nbsp; <i>All architectures</i><br>
 Avoid possible hijacking of X11-forwarded connections with sshd(8)
 by refusing to listen on a port unless all address families bind
 successfully.<br>
@@ -232,7 +244,8 @@
 <p>
 
 <li><a name="001_openssh"></a>
-<font color="#009000"><strong>001: SECURITY FIX: March 30, 2008</strong></font> &nbsp; <i>All architectures</i><br>
+<font color="#009000"><strong>001: SECURITY FIX: March 30, 2008</strong></font>
+&nbsp; <i>All architectures</i><br>
 sshd(8) would execute ~/.ssh/rc even when a sshd_config(5) <em>ForceCommand</em>
 directive was in effect, allowing users with write access to this file to
 execute arbitrary commands. This behaviour was documented, but was an unsafe