===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/errata58.html,v
retrieving revision 1.36
retrieving revision 1.37
diff -c -r1.36 -r1.37
*** www/errata58.html	2017/03/28 04:04:52	1.36
--- www/errata58.html	2017/03/28 06:41:18	1.37
***************
*** 71,77 ****
  <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.8.tar.gz">tar.gz file</a>
--- 71,77 ----
  <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.8/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.8.tar.gz">tar.gz file</a>
***************
*** 85,91 ****
  
  <ul>
  
! <li id="001_sshd">
  <font color="#009000"><strong>001: SECURITY FIX: August 30, 2015</strong></font>
  &nbsp; <i>All architectures</i><br>
  Inverted logic made PermitRootLogin "prohibit-password" unsafe.
--- 85,91 ----
  
  <ul>
  
! <li id="p001_sshd">
  <font color="#009000"><strong>001: SECURITY FIX: August 30, 2015</strong></font>
  &nbsp; <i>All architectures</i><br>
  Inverted logic made PermitRootLogin "prohibit-password" unsafe.
***************
*** 95,101 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="002_sslhello">
  <font color="#009000"><strong>002: INTEROPERABILITY FIX: August 30, 2015</strong></font>
  &nbsp; <i>All architectures</i><br>
  LibreSSL 2.2.2 incorrectly handles ClientHello messages that do not
--- 95,101 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p002_sslhello">
  <font color="#009000"><strong>002: INTEROPERABILITY FIX: August 30, 2015</strong></font>
  &nbsp; <i>All architectures</i><br>
  LibreSSL 2.2.2 incorrectly handles ClientHello messages that do not
***************
*** 105,111 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="003_uvm">
  <font color="#009000"><strong>003: RELIABILITY FIX: September 28, 2015</strong></font>
  &nbsp; <i>All architectures</i><br>
  An incorrect operation in uvm could result in system panics.
--- 105,111 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p003_uvm">
  <font color="#009000"><strong>003: RELIABILITY FIX: September 28, 2015</strong></font>
  &nbsp; <i>All architectures</i><br>
  An incorrect operation in uvm could result in system panics.
***************
*** 114,120 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="004_smtpd">
  <font color="#009000"><strong>004: SECURITY FIX: October 1, 2015</strong></font>
  &nbsp; <i>All architectures</i><br>
  Fix multiple reliability and security issues in smtpd:<br>
--- 114,120 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p004_smtpd">
  <font color="#009000"><strong>004: SECURITY FIX: October 1, 2015</strong></font>
  &nbsp; <i>All architectures</i><br>
  Fix multiple reliability and security issues in smtpd:<br>
***************
*** 133,139 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="005_kevent">
  <font color="#009000"><strong>005: RELIABILITY FIX: October 14, 2015</strong></font>
  &nbsp; <i>All architectures</i><br>
  A problem with timer kevents could result in a kernel hang (local denial
--- 133,139 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p005_kevent">
  <font color="#009000"><strong>005: RELIABILITY FIX: October 14, 2015</strong></font>
  &nbsp; <i>All architectures</i><br>
  A problem with timer kevents could result in a kernel hang (local denial
***************
*** 142,148 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="006_src">
  <font color="#009000"><strong>006: RELEASE CD ISSUE: Oct 18, 2015</strong></font>
  &nbsp; <i>All architectures</i><br>
  The "src.tar.gz" file on the source tree was created on the wrong day,
--- 142,148 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p006_src">
  <font color="#009000"><strong>006: RELEASE CD ISSUE: Oct 18, 2015</strong></font>
  &nbsp; <i>All architectures</i><br>
  The "src.tar.gz" file on the source tree was created on the wrong day,
***************
*** 153,159 ****
  A replacement file is available</a> in the 5.8 release directory with the name <b>cd-src.tar.gz</b>; due to size of the file, check local mirrors also.
  <p>
  
! <li id="007_obj2txt">
  <font color="#009000"><strong>007: RELIABILITY FIX: October 15, 2015</strong></font>
  &nbsp; <i>All architectures</i><br>
  The OBJ_obj2txt function in libcrypto contains a one byte buffer overrun
--- 153,159 ----
  A replacement file is available</a> in the 5.8 release directory with the name <b>cd-src.tar.gz</b>; due to size of the file, check local mirrors also.
  <p>
  
! <li id="p007_obj2txt">
  <font color="#009000"><strong>007: RELIABILITY FIX: October 15, 2015</strong></font>
  &nbsp; <i>All architectures</i><br>
  The OBJ_obj2txt function in libcrypto contains a one byte buffer overrun
***************
*** 162,168 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="008_rsn">
  <font color="#009000"><strong>008: RELIABILITY FIX: November 9, 2015</strong></font>
  &nbsp; <i>All architectures</i><br>
  Insufficient validation of RSN element group cipher values in 802.11
--- 162,168 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p008_rsn">
  <font color="#009000"><strong>008: RELIABILITY FIX: November 9, 2015</strong></font>
  &nbsp; <i>All architectures</i><br>
  Insufficient validation of RSN element group cipher values in 802.11
***************
*** 171,177 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="009_clientcert">
  <font color="#009000"><strong>009: RELIABILITY FIX: Dec 3, 2015</strong></font>
  &nbsp; <i>All architectures</i><br>
  A NULL pointer dereference could be triggered by a crafted certificate sent to
--- 171,177 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p009_clientcert">
  <font color="#009000"><strong>009: RELIABILITY FIX: Dec 3, 2015</strong></font>
  &nbsp; <i>All architectures</i><br>
  A NULL pointer dereference could be triggered by a crafted certificate sent to
***************
*** 180,186 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="010_sshd">
  <font color="#009000"><strong>010: SECURITY FIX: January 14, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Experimental roaming code in the ssh client could be tricked by a hostile sshd
--- 180,186 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p010_sshd">
  <font color="#009000"><strong>010: SECURITY FIX: January 14, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Experimental roaming code in the ssh client could be tricked by a hostile sshd
***************
*** 193,199 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="011_sshd">
  <font color="#009000"><strong>011: SECURITY FIX: March 10, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  <a href="https://www.openssh.com/txt/x11fwd.adv">
--- 193,199 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p011_sshd">
  <font color="#009000"><strong>011: SECURITY FIX: March 10, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  <a href="https://www.openssh.com/txt/x11fwd.adv">
***************
*** 206,212 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="012_in6bind">
  <font color="#009000"><strong>012: SECURITY FIX: March 16, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Insufficient checks in IPv6 socket binding and UDP IPv6 option
--- 206,212 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p012_in6bind">
  <font color="#009000"><strong>012: SECURITY FIX: March 16, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Insufficient checks in IPv6 socket binding and UDP IPv6 option
***************
*** 217,223 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="013_crypto">
  <font color="#009000"><strong>013: SECURITY FIX: May 3, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Fix issues in the libcrypto library.
--- 217,223 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p013_crypto">
  <font color="#009000"><strong>013: SECURITY FIX: May 3, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Fix issues in the libcrypto library.
***************
*** 234,240 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="014_uvideo">
  <font color="#009000"><strong>014: SECURITY FIX: May 17, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Insufficient checks in the uvideo(4) V4L2 ioctl handling leak kernel
--- 234,240 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p014_uvideo">
  <font color="#009000"><strong>014: SECURITY FIX: May 17, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Insufficient checks in the uvideo(4) V4L2 ioctl handling leak kernel
***************
*** 244,250 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="015_crypto">
  <font color="#009000"><strong>015: 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.
--- 244,250 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p015_crypto">
  <font color="#009000"><strong>015: 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.
***************
*** 253,259 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="016_libexpat">
  <font color="#009000"><strong>016: SECURITY FIX: June 2, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Fix issues in the libexpat library to prevent multiple integer and buffer overflows.
--- 253,259 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p016_libexpat">
  <font color="#009000"><strong>016: SECURITY FIX: June 2, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Fix issues in the libexpat library to prevent multiple integer and buffer overflows.
***************
*** 262,268 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="017_crypto">
  <font color="#009000"><strong>017: SECURITY FIX: June 6, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Correct a problem that prevents the DSA signing algorithm from running
--- 262,268 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p017_crypto">
  <font color="#009000"><strong>017: SECURITY FIX: June 6, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Correct a problem that prevents the DSA signing algorithm from running
***************
*** 272,278 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="018_splice">
  <font color="#009000"><strong>018: RELIABILITY FIX: July 14, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Splicing sockets in a loop could cause a kernel spin.
--- 272,278 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p018_splice">
  <font color="#009000"><strong>018: RELIABILITY FIX: July 14, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Splicing sockets in a loop could cause a kernel spin.
***************
*** 281,287 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="019_dirent">
  <font color="#009000"><strong>019: 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.
--- 281,287 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p019_dirent">
  <font color="#009000"><strong>019: 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.
***************
*** 290,296 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="020_mmap">
  <font color="#009000"><strong>020: SECURITY FIX: July 14, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  The mmap extension __MAP_NOFAULT could overcommit resources and crash
--- 290,296 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p020_mmap">
  <font color="#009000"><strong>020: SECURITY FIX: July 14, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  The mmap extension __MAP_NOFAULT could overcommit resources and crash
***************
*** 300,306 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="021_timeout">
  <font color="#009000"><strong>021: RELIABILITY FIX: July 14, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Tick counting overflows could cause a kernel crash.
--- 300,306 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p021_timeout">
  <font color="#009000"><strong>021: RELIABILITY FIX: July 14, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Tick counting overflows could cause a kernel crash.
***************
*** 309,315 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="022_kevent">
  <font color="#009000"><strong>022: 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.
--- 309,315 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p022_kevent">
  <font color="#009000"><strong>022: 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.
***************
*** 318,324 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="023_amap">
  <font color="#009000"><strong>023: RELIABILITY FIX: July 14, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Unchecked parameters and integer overflows in the amap allocation routines
--- 318,324 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p023_amap">
  <font color="#009000"><strong>023: RELIABILITY FIX: July 14, 2016</strong></font>
  &nbsp; <i>All architectures</i><br>
  Unchecked parameters and integer overflows in the amap allocation routines
***************
*** 329,335 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="024_relayd">
  <font color="#009000"><strong>024: 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
--- 329,335 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p024_relayd">
  <font color="#009000"><strong>024: 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
***************
*** 339,345 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="025_sysctl">
  <font color="#009000">
  <strong>025: RELIABILITY FIX: August 2, 2016</strong></font>
  &nbsp; <i>All architectures</i>
--- 339,345 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p025_sysctl">
  <font color="#009000">
  <strong>025: RELIABILITY FIX: August 2, 2016</strong></font>
  &nbsp; <i>All architectures</i>
***************
*** 350,356 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="026_uvmisavail">
  <font color="#009000">
  <strong>026: RELIABILITY FIX: August 2, 2016</strong></font>
  &nbsp; <i>All architectures</i>
--- 350,356 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p026_uvmisavail">
  <font color="#009000">
  <strong>026: RELIABILITY FIX: August 2, 2016</strong></font>
  &nbsp; <i>All architectures</i>
***************
*** 361,367 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="027_perl">
  <font color="#009000">
  <strong>027: SECURITY FIX: August 6, 2016</strong></font>
  &nbsp; <i>All architectures</i>
--- 361,367 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p027_perl">
  <font color="#009000">
  <strong>027: SECURITY FIX: August 6, 2016</strong></font>
  &nbsp; <i>All architectures</i>
***************
*** 374,380 ****
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="028_relayd">
  <font color="#009000">
  <strong>028: RELIABILITY FIX: August 6, 2016</strong></font>
  &nbsp; <i>All architectures</i>
--- 374,380 ----
  A source code patch exists which remedies this problem.</a>
  <p>
  
! <li id="p028_relayd">
  <font color="#009000">
  <strong>028: RELIABILITY FIX: August 6, 2016</strong></font>
  &nbsp; <i>All architectures</i>