===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/errata44.html,v
retrieving revision 1.58
retrieving revision 1.59
diff -c -r1.58 -r1.59
*** www/errata44.html	2017/03/28 04:04:52	1.58
--- www/errata44.html	2017/03/28 06:41:18	1.59
***************
*** 82,88 ****
  <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,
--- 82,88 ----
  <hr>
  
  <ul>
! <li id="p016_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,
***************
*** 92,98 ****
  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.
--- 92,98 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p015_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.
***************
*** 101,107 ****
  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
--- 101,107 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p014_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
***************
*** 113,119 ****
  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,
--- 113,119 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p013_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,
***************
*** 134,140 ****
  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
--- 134,140 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p012_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
***************
*** 152,158 ****
  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
--- 152,158 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p011_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
***************
*** 165,171 ****
  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
--- 165,171 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p010_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
***************
*** 175,181 ****
  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 -
--- 175,181 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p009_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 -
***************
*** 188,194 ****
  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
--- 188,194 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p008_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
***************
*** 200,206 ****
  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
--- 200,206 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p007_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
***************
*** 214,220 ****
  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
--- 214,220 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p006_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
***************
*** 225,231 ****
  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
--- 225,231 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p005_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
***************
*** 235,245 ****
  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
! <a href="http://man.openbsd.org/?query=httpd&sektion=8">httpd(8)</a>'s
  mod_proxy module which is broken on 64-bit architectures. Due to the bug this
  will result in child processes crashing when utilizing proxy rules during an
  HTTP session.
--- 235,245 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p004_httpd">
  <font color="#009000"><strong>004: RELIABILITY FIX: November 6, 2008</strong></font>
  &nbsp; <i>All architectures</i><br>
  Fix
! <a href="http://man.openbsd.org/OpenBSD-4.4/httpd.8">httpd(8)</a>'s
  mod_proxy module which is broken on 64-bit architectures. Due to the bug this
  will result in child processes crashing when utilizing proxy rules during an
  HTTP session.
***************
*** 248,254 ****
  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
--- 248,254 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p003_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
***************
*** 259,265 ****
  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)
--- 259,265 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p002_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)
***************
*** 269,275 ****
  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
--- 269,275 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p001_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