===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/errata46.html,v
retrieving revision 1.47
retrieving revision 1.48
diff -c -r1.47 -r1.48
*** www/errata46.html	2017/03/28 04:04:52	1.47
--- www/errata46.html	2017/03/28 06:41:18	1.48
***************
*** 82,88 ****
  <hr>
  
  <ul>
! <li id="012_trunklacp">
  <font color="#009000"><strong>012: RELIABILITY FIX: May 14, 2010</strong></font>
  &nbsp; <i>All architectures</i><br>
  Insufficient protection of the trunk interface queues may cause
--- 82,88 ----
  <hr>
  
  <ul>
! <li id="p012_trunklacp">
  <font color="#009000"><strong>012: RELIABILITY FIX: May 14, 2010</strong></font>
  &nbsp; <i>All architectures</i><br>
  Insufficient protection of the trunk interface queues may cause
***************
*** 92,98 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="011_pfsync">
  <font color="#009000"><strong>011: RELIABILITY FIX: May 14, 2010</strong></font>
  &nbsp; <i>All architectures</i><br>
  Incorrectly initialized state updates can cause pfsync update storms.
--- 92,98 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p011_pfsync">
  <font color="#009000"><strong>011: RELIABILITY FIX: May 14, 2010</strong></font>
  &nbsp; <i>All architectures</i><br>
  Incorrectly initialized state updates can cause pfsync update storms.
***************
*** 101,107 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="010_openssl">
  <font color="#009000"><strong>010: SECURITY FIX: April 14, 2010</strong></font>
  &nbsp; <i>All architectures</i><br>
  In TLS connections, certain incorrectly formatted records can cause
--- 101,107 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p010_openssl">
  <font color="#009000"><strong>010: SECURITY FIX: April 14, 2010</strong></font>
  &nbsp; <i>All architectures</i><br>
  In TLS connections, certain incorrectly formatted records can cause
***************
*** 111,121 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="009_mpi">
  <font color="#009000"><strong>009: RELIABILITY FIX: April 4, 2010</strong></font>
  &nbsp; <i>All architectures</i><br>
  When updating sensors showing the state of RAID volumes
! <a href="http://man.openbsd.org/?query=mpi&sektion=4">mpi(4)</a>
  allocates temporary memory and then returns it to the kernel as
  device memory.
  This causes kernel memory usage to be misrepresented, eventually
--- 111,121 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p009_mpi">
  <font color="#009000"><strong>009: RELIABILITY FIX: April 4, 2010</strong></font>
  &nbsp; <i>All architectures</i><br>
  When updating sensors showing the state of RAID volumes
! <a href="http://man.openbsd.org/OpenBSD-4.6/mpi.4">mpi(4)</a>
  allocates temporary memory and then returns it to the kernel as
  device memory.
  This causes kernel memory usage to be misrepresented, eventually
***************
*** 126,132 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="008_kerberos">
  <font color="#009000"><strong>008: RELIABILITY FIX: March 31, 2010</strong></font>
  &nbsp; <i>All architectures</i><br>
  When decrypting packets, the internal decryption functions were not
--- 126,132 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p008_kerberos">
  <font color="#009000"><strong>008: RELIABILITY FIX: March 31, 2010</strong></font>
  &nbsp; <i>All architectures</i><br>
  When decrypting packets, the internal decryption functions were not
***************
*** 137,143 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="007_ftpd">
  <font color="#009000"><strong>007: 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
--- 137,143 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p007_ftpd">
  <font color="#009000"><strong>007: 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
***************
*** 147,153 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="006_openssl">
  <font color="#009000"><strong>006: SECURITY FIX: March 12, 2010</strong></font>
  &nbsp; <i>All architectures</i><br>
  OpenSSL is susceptible to a buffer overflow due to a failure
--- 147,153 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p006_openssl">
  <font color="#009000"><strong>006: SECURITY FIX: March 12, 2010</strong></font>
  &nbsp; <i>All architectures</i><br>
  OpenSSL is susceptible to a buffer overflow due to a failure
***************
*** 157,163 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="005_ptrace">
  <font color="#009000"><strong>005: 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
--- 157,163 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p005_ptrace">
  <font color="#009000"><strong>005: 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
***************
*** 168,174 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="004_openssl">
  <font color="#009000"><strong>004: 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
--- 168,174 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p004_openssl">
  <font color="#009000"><strong>004: 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
***************
*** 180,186 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="003_getsockopt">
  <font color="#009000"><strong>003: 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,
--- 180,186 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p003_getsockopt">
  <font color="#009000"><strong>003: 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,
***************
*** 190,196 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="002_xmm">
  <font color="#009000"><strong>002: RELIABILITY FIX: October 05, 2009</strong></font>
  &nbsp; <i>i386 only</i><br>
  XMM exceptions are not correctly handled resulting in a kernel panic.
--- 190,196 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p002_xmm">
  <font color="#009000"><strong>002: RELIABILITY FIX: October 05, 2009</strong></font>
  &nbsp; <i>i386 only</i><br>
  XMM exceptions are not correctly handled resulting in a kernel panic.
***************
*** 199,205 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="001_bind">
  <font color="#009000"><strong>001: RELIABILITY FIX: July 29, 2009</strong></font>
  &nbsp; <i>All architectures</i><br>
  A vulnerability has been found in BIND's named server
--- 199,205 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p001_bind">
  <font color="#009000"><strong>001: RELIABILITY FIX: July 29, 2009</strong></font>
  &nbsp; <i>All architectures</i><br>
  A vulnerability has been found in BIND's named server