===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/errata45.html,v
retrieving revision 1.39
retrieving revision 1.40
diff -c -r1.39 -r1.40
*** www/errata45.html	2014/10/02 14:34:45	1.39
--- www/errata45.html	2015/02/14 04:36:51	1.40
***************
*** 81,87 ****
  <hr>
  
  <ul>
! <li><a name="016_openssl"></a>
  <font color="#009000"><strong>016: SECURITY FIX: April 14, 2010</strong></font>
  &nbsp; <i>All architectures</i><br>
  In TLS connections, certain incorrectly formatted records can cause
--- 81,87 ----
  <hr>
  
  <ul>
! <li id="016_openssl">
  <font color="#009000"><strong>016: SECURITY FIX: April 14, 2010</strong></font>
  &nbsp; <i>All architectures</i><br>
  In TLS connections, certain incorrectly formatted records can cause
***************
*** 91,97 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="015_mpi"></a>
  <font color="#009000"><strong>015: RELIABILITY FIX: April 4, 2010</strong></font>
  &nbsp; <i>All architectures</i><br>
  When updating sensors showing the state of RAID volumes
--- 91,97 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="015_mpi">
  <font color="#009000"><strong>015: RELIABILITY FIX: April 4, 2010</strong></font>
  &nbsp; <i>All architectures</i><br>
  When updating sensors showing the state of RAID volumes
***************
*** 106,112 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="014_kerberos"></a>
  <font color="#009000"><strong>014: RELIABILITY FIX: March 31, 2010</strong></font>
  &nbsp; <i>All architectures</i><br>
  When decrypting packets, the internal decryption functions were not
--- 106,112 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="014_kerberos">
  <font color="#009000"><strong>014: RELIABILITY FIX: March 31, 2010</strong></font>
  &nbsp; <i>All architectures</i><br>
  When decrypting packets, the internal decryption functions were not
***************
*** 117,123 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="013_ftpd"></a>
  <font color="#009000"><strong>013: RELIABILITY FIX: March 12, 2010</strong></font>
  &nbsp; <i>All architectures</i><br>
  Due to a null pointer dereference, it would be possible to crash ftpd when
--- 117,123 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="013_ftpd">
  <font color="#009000"><strong>013: RELIABILITY FIX: March 12, 2010</strong></font>
  &nbsp; <i>All architectures</i><br>
  Due to a null pointer dereference, it would be possible to crash ftpd when
***************
*** 127,133 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="012_openssl"></a>
  <font color="#009000"><strong>012: SECURITY FIX: March 12, 2010</strong></font>
  &nbsp; <i>All architectures</i><br>
  OpenSSL is susceptible to a buffer overflow due to a failure
--- 127,133 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="012_openssl">
  <font color="#009000"><strong>012: SECURITY FIX: March 12, 2010</strong></font>
  &nbsp; <i>All architectures</i><br>
  OpenSSL is susceptible to a buffer overflow due to a failure
***************
*** 137,143 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="011_ptrace"></a>
  <font color="#009000"><strong>011: RELIABILITY FIX: January 29, 2010</strong></font>
  &nbsp; <i>All architectures</i><br>
  By using ptrace(2) on an ancestor process, a loop in the process tree
--- 137,143 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="011_ptrace">
  <font color="#009000"><strong>011: RELIABILITY FIX: January 29, 2010</strong></font>
  &nbsp; <i>All architectures</i><br>
  By using ptrace(2) on an ancestor process, a loop in the process tree
***************
*** 148,154 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="010_openssl"></a>
  <font color="#009000"><strong>010: SECURITY FIX: November 26, 2009</strong></font>
  &nbsp; <i>All architectures</i><br>
  The SSL/TLS protocol is subject to man-in-the-middle attacks related to
--- 148,154 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="010_openssl">
  <font color="#009000"><strong>010: SECURITY FIX: November 26, 2009</strong></font>
  &nbsp; <i>All architectures</i><br>
  The SSL/TLS protocol is subject to man-in-the-middle attacks related to
***************
*** 160,166 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="009_getsockopt"></a>
  <font color="#009000"><strong>009: 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,
--- 160,166 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="009_getsockopt">
  <font color="#009000"><strong>009: 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,
***************
*** 170,176 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="008_xmm"></a>
  <font color="#009000"><strong>008: RELIABILITY FIX: October 05, 2009</strong></font>
  &nbsp; <i>i386 only</i><br>
  XMM exceptions are not correctly handled resulting in a kernel panic.
--- 170,176 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="008_xmm">
  <font color="#009000"><strong>008: RELIABILITY FIX: October 05, 2009</strong></font>
  &nbsp; <i>i386 only</i><br>
  XMM exceptions are not correctly handled resulting in a kernel panic.
***************
*** 179,185 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="007_bind"></a>
  <font color="#009000"><strong>007: RELIABILITY FIX: July 29, 2009</strong></font>
  &nbsp; <i>All architectures</i><br>
  A vulnerability has been found in BIND's named server
--- 179,185 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="007_bind">
  <font color="#009000"><strong>007: RELIABILITY FIX: July 29, 2009</strong></font>
  &nbsp; <i>All architectures</i><br>
  A vulnerability has been found in BIND's named server
***************
*** 191,197 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="006_perl"></a>
  <font color="#009000"><strong>006: RELIABILITY FIX: June 24, 2009</strong></font>
  &nbsp; <i>All architectures</i><br>
  An off-by-one error in the inflate function in Zlib.xs in the
--- 191,197 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="006_perl">
  <font color="#009000"><strong>006: RELIABILITY FIX: June 24, 2009</strong></font>
  &nbsp; <i>All architectures</i><br>
  An off-by-one error in the inflate function in Zlib.xs in the
***************
*** 206,212 ****
  <p>
  
  
! <li><a name="005_audio"></a>
  <font color="#009000"><strong>005: RELIABILITY FIX: April 24, 2009</strong></font>
  &nbsp; <i>All architectures</i><br>
  On very high system load, an audio interrupt may occur while the
--- 206,212 ----
  <p>
  
  
! <li id="005_audio">
  <font color="#009000"><strong>005: RELIABILITY FIX: April 24, 2009</strong></font>
  &nbsp; <i>All architectures</i><br>
  On very high system load, an audio interrupt may occur while the
***************
*** 220,226 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="004_aucat"></a>
  <font color="#009000"><strong>004: RELIABILITY FIX: April 24, 2009</strong></font>
  &nbsp; <i>All architectures</i><br>
  In server mode when in full-duplex mode (the default)
--- 220,226 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="004_aucat">
  <font color="#009000"><strong>004: RELIABILITY FIX: April 24, 2009</strong></font>
  &nbsp; <i>All architectures</i><br>
  In server mode when in full-duplex mode (the default)
***************
*** 233,239 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="003_bus_dma"></a>
  <font color="#009000"><strong>003: RELIABILITY FIX: April 24, 2009</strong></font>
  &nbsp; <i>i386 only</i><br>
  When DMA'able memory is mapped by device drivers, the
--- 233,239 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="003_bus_dma">
  <font color="#009000"><strong>003: RELIABILITY FIX: April 24, 2009</strong></font>
  &nbsp; <i>i386 only</i><br>
  When DMA'able memory is mapped by device drivers, the
***************
*** 247,253 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="002_pf"></a>
  <font color="#009000"><strong>002: 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,
--- 247,253 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="002_pf">
  <font color="#009000"><strong>002: 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,
***************
*** 268,274 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li><a name="001_openssl"></a>
  <font color="#009000"><strong>001: 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
--- 268,274 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="001_openssl">
  <font color="#009000"><strong>001: 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