===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/errata44.html,v
retrieving revision 1.42
retrieving revision 1.43
diff -c -r1.42 -r1.43
*** www/errata44.html	2014/10/02 14:34:45	1.42
--- www/errata44.html	2015/02/14 04:36:51	1.43
***************
*** 81,87 ****
  <hr>
  
  <ul>
! <li><a name="016_getsockopt"></a>
  <font color="#009000"><strong>016: RELIABILITY FIX: October 28, 2009</strong></font>
  &nbsp; <i>All architectures</i><br>
  getsockopt(2) with any of IP_AUTH_LEVEL, IP_ESP_TRANS_LEVEL, IP_ESP_NETWORK_LEVEL,
--- 81,87 ----
  <hr>
  
  <ul>
! <li id="016_getsockopt">
  <font color="#009000"><strong>016: RELIABILITY FIX: October 28, 2009</strong></font>
  &nbsp; <i>All architectures</i><br>
  getsockopt(2) with any of IP_AUTH_LEVEL, IP_ESP_TRANS_LEVEL, IP_ESP_NETWORK_LEVEL,
***************
*** 91,97 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="015_xmm"></a>
  <font color="#009000"><strong>015: RELIABILITY FIX: October 05, 2009</strong></font>
  &nbsp; <i>i386 only</i><br>
  XMM exceptions are not correctly handled resulting in a kernel panic.
--- 91,97 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="015_xmm">
  <font color="#009000"><strong>015: RELIABILITY FIX: October 05, 2009</strong></font>
  &nbsp; <i>i386 only</i><br>
  XMM exceptions are not correctly handled resulting in a kernel panic.
***************
*** 100,106 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="014_bind"></a>
  <font color="#009000"><strong>014: RELIABILITY FIX: July 29, 2009</strong></font>
  &nbsp; <i>All architectures</i><br>
  A vulnerability has been found in BIND's named server
--- 100,106 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="014_bind">
  <font color="#009000"><strong>014: RELIABILITY FIX: July 29, 2009</strong></font>
  &nbsp; <i>All architectures</i><br>
  A vulnerability has been found in BIND's named server
***************
*** 112,118 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="013_pf"></a>
  <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,
--- 112,118 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="013_pf">
  <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,
***************
*** 133,139 ****
  A source code patch exists which remedies this problem.</a>
  <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>
  The OpenSSL ASN.1 handling code could be forced to perform invalid memory
--- 133,139 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="012_openssl">
  <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
***************
*** 151,157 ****
  A source code patch exists which remedies this problem.</a>
  <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>
  sudo(8) may allow a user listed in the sudoers file to run a command
--- 151,157 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="011_sudo">
  <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
***************
*** 164,170 ****
  A source code patch exists which remedies this problem.</a>
  <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>
  bgpd(8) did not correctly prepend its own AS to very long AS paths, causing
--- 164,170 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="010_bgpd">
  <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
***************
*** 174,180 ****
  A source code patch exists which remedies this problem.</a>
  <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>
  Upon reception of an invalid update with 4-byte AS attributes, bgpd -
--- 174,180 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="009_bgpd">
  <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 -
***************
*** 187,193 ****
  A source code patch exists which remedies this problem.</a>
  <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>
  named(8) did not correctly check the return value of a DSA verification
--- 187,193 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="008_bind">
  <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
***************
*** 199,205 ****
  A source code patch exists which remedies this problem.</a>
  <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>
  The OpenSSL libraries did not correctly check the return value from
--- 199,205 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="007_openssl">
  <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
***************
*** 213,219 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="006_dhcpd"></a>
  <font color="#009000"><strong>006: RELIABILITY FIX: November 19, 2008</strong></font>
  &nbsp; <i>All architectures</i><br>
  Due to changes in the options handling this caused problems with some
--- 213,219 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="006_dhcpd">
  <font color="#009000"><strong>006: RELIABILITY FIX: November 19, 2008</strong></font>
  &nbsp; <i>All architectures</i><br>
  Due to changes in the options handling this caused problems with some
***************
*** 224,230 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="005_pglistalloc"></a>
  <font color="#009000"><strong>005: RELIABILITY FIX: November 7, 2008</strong></font>
  &nbsp; <i>All architectures</i><br>
  A software bug could cause memory allocation to cause a kernel panic
--- 224,230 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="005_pglistalloc">
  <font color="#009000"><strong>005: RELIABILITY FIX: November 7, 2008</strong></font>
  &nbsp; <i>All architectures</i><br>
  A software bug could cause memory allocation to cause a kernel panic
***************
*** 234,240 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="004_httpd"></a>
  <font color="#009000"><strong>004: RELIABILITY FIX: November 6, 2008</strong></font>
  &nbsp; <i>All architectures</i><br>
  Fix
--- 234,240 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="004_httpd">
  <font color="#009000"><strong>004: RELIABILITY FIX: November 6, 2008</strong></font>
  &nbsp; <i>All architectures</i><br>
  Fix
***************
*** 247,253 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="003_tcpinput"></a>
  <font color="#009000"><strong>003: RELIABILITY FIX: November 6, 2008</strong></font>
  &nbsp; <i>All architectures</i><br>
  Fix the IPv4 TCP/IP stack's TIME_WAIT socket recycling. Due to the bug this
--- 247,253 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="003_tcpinput">
  <font color="#009000"><strong>003: RELIABILITY FIX: November 6, 2008</strong></font>
  &nbsp; <i>All architectures</i><br>
  Fix the IPv4 TCP/IP stack's TIME_WAIT socket recycling. Due to the bug this
***************
*** 258,264 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="002_vr"></a>
  <font color="#009000"><strong>002: RELIABILITY FIX: November 2, 2008</strong></font>
  &nbsp; <i>All architectures</i><br>
  Due to a bug in the vr(4) driver it is possible for a system using the vr(4)
--- 258,264 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="002_vr">
  <font color="#009000"><strong>002: RELIABILITY FIX: November 2, 2008</strong></font>
  &nbsp; <i>All architectures</i><br>
  Due to a bug in the vr(4) driver it is possible for a system using the vr(4)
***************
*** 268,274 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="001_ndp"></a>
  <font color="#009000"><strong>001: SECURITY FIX: November 2, 2008</strong></font>
  &nbsp; <i>All architectures</i><br>
  The Neighbor Discovery Protocol (ndp) did not correctly verify neighbor
--- 268,274 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="001_ndp">
  <font color="#009000"><strong>001: SECURITY FIX: November 2, 2008</strong></font>
  &nbsp; <i>All architectures</i><br>
  The Neighbor Discovery Protocol (ndp) did not correctly verify neighbor