===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/errata59.html,v
retrieving revision 1.38
retrieving revision 1.39
diff -c -r1.38 -r1.39
*** www/errata59.html	2017/03/27 20:25:28	1.38
--- www/errata59.html	2017/03/28 06:41:18	1.39
***************
*** 70,76 ****
  <p>
  Patches for the OpenBSD base system are distributed as unified diffs.
  Each patch is cryptographically signed with the
! <a href="http://man.openbsd.org/signify">signify(1)</a> tool and contains
  usage instructions.
  All the following patches are also available in one
  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/5.9.tar.gz">tar.gz file</a>
--- 70,76 ----
  <p>
  Patches for the OpenBSD base system are distributed as unified diffs.
  Each patch is cryptographically signed with the
! <a href="http://man.openbsd.org/OpenBSD-5.9/signify.1">signify(1)</a> tool and contains
  usage instructions.
  All the following patches are also available in one
  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/5.9.tar.gz">tar.gz file</a>
***************
*** 85,91 ****
  
  <ul>
  
! <li id="001_sshd">
  <font color="#009000"><strong>001: SECURITY FIX: March 10, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  <a href="https://www.openssh.com/txt/x11fwd.adv">
--- 85,91 ----
  
  <ul>
  
! <li id="p001_sshd">
  <font color="#009000"><strong>001: SECURITY FIX: March 10, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  <a href="https://www.openssh.com/txt/x11fwd.adv">
***************
*** 98,104 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="002_in6bind">
  <font color="#009000"><strong>002: SECURITY FIX: March 16, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Insufficient checks in IPv6 socket binding and UDP IPv6 option
--- 98,104 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p002_in6bind">
  <font color="#009000"><strong>002: SECURITY FIX: March 16, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Insufficient checks in IPv6 socket binding and UDP IPv6 option
***************
*** 109,115 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="003_pledge">
  <font color="#009000"><strong>003: RELIABILITY FIX: March 16, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Incorrect path processing in pledge_namei() could result in unexpected
--- 109,115 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p003_pledge">
  <font color="#009000"><strong>003: RELIABILITY FIX: March 16, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Incorrect path processing in pledge_namei() could result in unexpected
***************
*** 119,125 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="004_mbuf">
  <font color="#009000"><strong>004: RELIABILITY FIX: April 30, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  A problem in m_dup_pkt() can result in kernel crashes with carp(4).
--- 119,125 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p004_mbuf">
  <font color="#009000"><strong>004: RELIABILITY FIX: April 30, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  A problem in m_dup_pkt() can result in kernel crashes with carp(4).
***************
*** 128,134 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="005_crypto">
  <font color="#009000"><strong>005: SECURITY FIX: May 3, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Fix issues in the libcrypto library.
--- 128,134 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p005_crypto">
  <font color="#009000"><strong>005: SECURITY FIX: May 3, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Fix issues in the libcrypto library.
***************
*** 144,150 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="006_smtpd">
  <font color="#009000"><strong>006: RELIABILITY FIX: May 16, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Fix issues in smtpd.
--- 144,150 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p006_smtpd">
  <font color="#009000"><strong>006: RELIABILITY FIX: May 16, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Fix issues in smtpd.
***************
*** 156,162 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="007_uvideo">
  <font color="#009000"><strong>007: SECURITY FIX: May 17, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Insufficient checks in the uvideo(4) V4L2 ioctl handling leak kernel
--- 156,162 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p007_uvideo">
  <font color="#009000"><strong>007: SECURITY FIX: May 17, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Insufficient checks in the uvideo(4) V4L2 ioctl handling leak kernel
***************
*** 166,172 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="008_bnx">
  <font color="#009000"><strong>008: RELIABILITY FIX: May 18, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Fix issue in the bnx(4) ethernet driver that could cause data corruption.
--- 166,172 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p008_bnx">
  <font color="#009000"><strong>008: RELIABILITY FIX: May 18, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Fix issue in the bnx(4) ethernet driver that could cause data corruption.
***************
*** 175,181 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="009_crypto">
  <font color="#009000"><strong>009: RELIABILITY FIX: May 29, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Fix a bug in the libcrypto library when parsing certain ASN.1 elements.
--- 175,181 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p009_crypto">
  <font color="#009000"><strong>009: RELIABILITY FIX: May 29, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Fix a bug in the libcrypto library when parsing certain ASN.1 elements.
***************
*** 184,190 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="010_libexpat">
  <font color="#009000"><strong>010: SECURITY FIX: June 2, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Fix issues in the libexpat library to prevent multiple integer and
--- 184,190 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p010_libexpat">
  <font color="#009000"><strong>010: SECURITY FIX: June 2, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Fix issues in the libexpat library to prevent multiple integer and
***************
*** 194,200 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="011_crypto">
  <font color="#009000"><strong>011: SECURITY FIX: June 6, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Correct a problem that prevents the DSA signing algorithm from running
--- 194,200 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p011_crypto">
  <font color="#009000"><strong>011: SECURITY FIX: June 6, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Correct a problem that prevents the DSA signing algorithm from running
***************
*** 204,210 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="012_crypto">
  <font color="#009000"><strong>012: SECURITY FIX: June 27, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Correct a problem that could result in incorrect parsing/encoding of times in OCSP messages.
--- 204,210 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p012_crypto">
  <font color="#009000"><strong>012: SECURITY FIX: June 27, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Correct a problem that could result in incorrect parsing/encoding of times in OCSP messages.
***************
*** 213,219 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="013_splice">
  <font color="#009000"><strong>013: RELIABILITY FIX: July 14, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Splicing sockets in a loop could cause a kernel spin.
--- 213,219 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p013_splice">
  <font color="#009000"><strong>013: RELIABILITY FIX: July 14, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Splicing sockets in a loop could cause a kernel spin.
***************
*** 222,228 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="014_unp">
  <font color="#009000"><strong>014: RELIABILITY FIX: July 14, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Multiple processes exiting with a fd-passing control message on a
--- 222,228 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p014_unp">
  <font color="#009000"><strong>014: RELIABILITY FIX: July 14, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Multiple processes exiting with a fd-passing control message on a
***************
*** 232,238 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="015_dirent">
  <font color="#009000"><strong>015: RELIABILITY FIX: July 14, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  ufs_readdir failed to limit size of memory allocation, leading to panics.
--- 232,238 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p015_dirent">
  <font color="#009000"><strong>015: RELIABILITY FIX: July 14, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  ufs_readdir failed to limit size of memory allocation, leading to panics.
***************
*** 241,247 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="016_mmap">
  <font color="#009000"><strong>016: SECURITY FIX: July 14, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  The mmap extension __MAP_NOFAULT could overcommit resources and crash
--- 241,247 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p016_mmap">
  <font color="#009000"><strong>016: SECURITY FIX: July 14, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  The mmap extension __MAP_NOFAULT could overcommit resources and crash
***************
*** 251,257 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="017_arp">
  <font color="#009000"><strong>017: RELIABILITY FIX: July 14, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  A race occuring in the unlocked ARP input path can lead to a kernel
--- 251,257 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p017_arp">
  <font color="#009000"><strong>017: RELIABILITY FIX: July 14, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  A race occuring in the unlocked ARP input path can lead to a kernel
***************
*** 261,267 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="018_timeout">
  <font color="#009000"><strong>018: RELIABILITY FIX: July 14, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Tick counting overflows could cause a kernel crash.
--- 261,267 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p018_timeout">
  <font color="#009000"><strong>018: RELIABILITY FIX: July 14, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Tick counting overflows could cause a kernel crash.
***************
*** 270,276 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="019_kevent">
  <font color="#009000"><strong>019: RELIABILITY FIX: July 14, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Invalid file descriptor use with kevent(2) could lead to a kernel crash.
--- 270,276 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p019_kevent">
  <font color="#009000"><strong>019: RELIABILITY FIX: July 14, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Invalid file descriptor use with kevent(2) could lead to a kernel crash.
***************
*** 279,285 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="020_amap">
  <font color="#009000"><strong>020: RELIABILITY FIX: July 14, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Unchecked parameters and integer overflows in the amap allocation routines
--- 279,285 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p020_amap">
  <font color="#009000"><strong>020: RELIABILITY FIX: July 14, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Unchecked parameters and integer overflows in the amap allocation routines
***************
*** 290,296 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="021_relayd">
  <font color="#009000"><strong>021: RELIABILITY FIX: July 25, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  When signaling an error to an HTTP relay client, the connection can be
--- 290,296 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p021_relayd">
  <font color="#009000"><strong>021: RELIABILITY FIX: July 25, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  When signaling an error to an HTTP relay client, the connection can be
***************
*** 300,306 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="022_sysctl">
  <font color="#009000">
  <strong>022: RELIABILITY FIX: August 2, 2016</strong></font>
  &nbsp; <i>All architectures</i>
--- 300,306 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p022_sysctl">
  <font color="#009000">
  <strong>022: RELIABILITY FIX: August 2, 2016</strong></font>
  &nbsp; <i>All architectures</i>
***************
*** 311,317 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="023_uvmisavail">
  <font color="#009000">
  <strong>023: RELIABILITY FIX: August 2, 2016</strong></font>
  &nbsp; <i>All architectures</i>
--- 311,317 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p023_uvmisavail">
  <font color="#009000">
  <strong>023: RELIABILITY FIX: August 2, 2016</strong></font>
  &nbsp; <i>All architectures</i>
***************
*** 322,328 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="024_perl">
  <font color="#009000">
  <strong>024: SECURITY FIX: August 6, 2016</strong></font>
  &nbsp; <i>All architectures</i>
--- 322,328 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p024_perl">
  <font color="#009000">
  <strong>024: SECURITY FIX: August 6, 2016</strong></font>
  &nbsp; <i>All architectures</i>
***************
*** 335,341 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="025_relayd">
  <font color="#009000">
  <strong>025: RELIABILITY FIX: August 6, 2016</strong></font>
  &nbsp; <i>All architectures</i>
--- 335,341 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p025_relayd">
  <font color="#009000">
  <strong>025: RELIABILITY FIX: August 6, 2016</strong></font>
  &nbsp; <i>All architectures</i>
***************
*** 347,353 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="026_wsfont">
  <font color="#009000">
  <strong>026: RELIABILITY FIX: September 17, 2016</strong></font>
  &nbsp; <i>All architectures</i>
--- 347,353 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p026_wsfont">
  <font color="#009000">
  <strong>026: RELIABILITY FIX: September 17, 2016</strong></font>
  &nbsp; <i>All architectures</i>
***************
*** 358,364 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="027_libssl">
  <font color="#009000">
  <strong>027: RELIABILITY FIX: September 22, 2016</strong></font>
  &nbsp; <i>All architectures</i>
--- 358,364 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p027_libssl">
  <font color="#009000">
  <strong>027: RELIABILITY FIX: September 22, 2016</strong></font>
  &nbsp; <i>All architectures</i>
***************
*** 370,376 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="028_libssl">
  <font color="#009000">
  <strong>028: SECURITY FIX: September 22, 2016</strong></font>
  &nbsp; <i>All architectures</i>
--- 370,376 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p028_libssl">
  <font color="#009000">
  <strong>028: SECURITY FIX: September 22, 2016</strong></font>
  &nbsp; <i>All architectures</i>
***************
*** 381,387 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="029_xorg_libs">
  <font color="#009000">
  <strong>029: SECURITY FIX: October 4, 2016</strong></font>
  &nbsp; <i>All architectures</i>
--- 381,387 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p029_xorg_libs">
  <font color="#009000">
  <strong>029: SECURITY FIX: October 4, 2016</strong></font>
  &nbsp; <i>All architectures</i>
***************
*** 393,399 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="030_ssh_kexinit">
  <font color="#009000">
  <strong>030: RELIABILITY FIX: October 10, 2016</strong></font>
  &nbsp; <i>All architectures</i>
--- 393,399 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p030_ssh_kexinit">
  <font color="#009000">
  <strong>030: RELIABILITY FIX: October 10, 2016</strong></font>
  &nbsp; <i>All architectures</i>
***************
*** 405,411 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="031_smtpd.patch">
  <font color="#009000">
  <strong>031: RELIABILITY FIX: October 13, 2016</strong></font>
  &nbsp; <i>All architectures</i>
--- 405,411 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p031_smtpd.patch">
  <font color="#009000">
  <strong>031: RELIABILITY FIX: October 13, 2016</strong></font>
  &nbsp; <i>All architectures</i>
***************
*** 416,422 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="032_libssl.patch">
  <font color="#009000">
  <strong>032: RELIABILITY FIX: November 5, 2016</strong></font>
  &nbsp; <i>All architectures</i>
--- 416,422 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p032_libssl.patch">
  <font color="#009000">
  <strong>032: RELIABILITY FIX: November 5, 2016</strong></font>
  &nbsp; <i>All architectures</i>
***************
*** 427,433 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="033_libcrypto.patch">
  <font color="#009000">
  <strong>033: SECURITY FIX: January 5, 2017</strong></font>
  &nbsp; <i>All architectures</i>
--- 427,433 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p033_libcrypto.patch">
  <font color="#009000">
  <strong>033: SECURITY FIX: January 5, 2017</strong></font>
  &nbsp; <i>All architectures</i>
***************
*** 438,444 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="034_httpd.patch">
  <font color="#009000">
  <strong>034: RELIABILITY FIX: January 31, 2017</strong></font>
  &nbsp; <i>All architectures</i>
--- 438,444 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p034_httpd.patch">
  <font color="#009000">
  <strong>034: RELIABILITY FIX: January 31, 2017</strong></font>
  &nbsp; <i>All architectures</i>
***************
*** 451,457 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="035_net80211.patch">
  <font color="#009000">
  <strong>035: SECURITY FIX: March 1, 2017</strong></font>
  &nbsp; <i>All architectures</i>
--- 451,457 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p035_net80211.patch">
  <font color="#009000">
  <strong>035: SECURITY FIX: March 1, 2017</strong></font>
  &nbsp; <i>All architectures</i>
***************
*** 463,469 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="036_pf.patch">
  <font color="#009000">
  <strong>036: RELIABILITY FIX: March 9, 2017</strong></font>
  &nbsp; <i>All architectures</i>
--- 463,469 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p036_pf.patch">
  <font color="#009000">
  <strong>036: RELIABILITY FIX: March 9, 2017</strong></font>
  &nbsp; <i>All architectures</i>
***************
*** 475,481 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="037_exec_elf.patch">
  <font color="#009000">
  <strong>037: SECURITY FIX: March 20, 2017</strong></font>
  &nbsp; <i>All architectures</i>
--- 475,481 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p037_exec_elf.patch">
  <font color="#009000">
  <strong>037: SECURITY FIX: March 20, 2017</strong></font>
  &nbsp; <i>All architectures</i>