[BACK]Return to errata26.html CVS log [TXT][DIR] Up to [local] / www

Diff for /www/errata26.html between version 1.84 and 1.85

version 1.84, 2019/04/02 12:46:56 version 1.85, 2019/05/27 22:55:19
Line 1 
Line 1 
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">  <!doctype html>
 <html>  <html lang=en id=errata>
 <head>  <meta charset=utf-8>
   
 <title>OpenBSD 2.6 Errata</title>  <title>OpenBSD 2.6 Errata</title>
 <meta name="description" content="the OpenBSD CD errata page">  <meta name="description" content="the OpenBSD CD errata page">
 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">  
 <meta name="viewport" content="width=device-width, initial-scale=1">  <meta name="viewport" content="width=device-width, initial-scale=1">
 <link rel="stylesheet" type="text/css" href="openbsd.css">  <link rel="stylesheet" type="text/css" href="openbsd.css">
 <link rel="canonical" href="https://www.openbsd.org/errata26.html">  <link rel="canonical" href="https://www.openbsd.org/errata26.html">
 </head>  
   
 <!--  <!--
                         IMPORTANT REMINDER                          IMPORTANT REMINDER
         IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE          IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE
 -->  -->
   
 <body bgcolor="#ffffff" text="#000000" link="#23238E">  
   
 <h2>  <h2 id=OpenBSD>
 <a href="index.html">  <a href="index.html">
 <font color="#0000ff"><i>Open</i></font><font color="#000084">BSD</font></a>  <i>Open</i><b>BSD</b></a>
 <font color="#e00000">2.6 Errata</font>  2.6 Errata
 </h2>  </h2>
 <hr>  <hr>
   
Line 87 
Line 85 
   
 <ul>  <ul>
 <li id="semconfig">  <li id="semconfig">
 <font color="#009000"><strong>024: SECURITY FIX: May 26, 2000</strong></font>  <strong>024: SECURITY FIX: May 26, 2000</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 Kernel contained an undocumented system call used to lock semaphore operations  Kernel contained an undocumented system call used to lock semaphore operations
 while they were being sampled by the ipcs(1) command.  This locking could be  while they were being sampled by the ipcs(1) command.  This locking could be
Line 98 
Line 96 
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
 <li id="ipf">  <li id="ipf">
 <font color="#009000"><strong>023: SECURITY FIX: May 25, 2000</strong></font>  <strong>023: SECURITY FIX: May 25, 2000</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 A misuse of ipf(8)  A misuse of ipf(8)
 <i>keep-state</i> rules can result in firewall rules being  <i>keep-state</i> rules can result in firewall rules being
Line 110 
Line 108 
 It updates ipf to version 3.3.16.  It updates ipf to version 3.3.16.
 <p>  <p>
 <li id="xlockmore">  <li id="xlockmore">
 <font color="#009000"><strong>022: SECURITY FIX: May 25, 2000</strong></font>  <strong>022: SECURITY FIX: May 25, 2000</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 xlockmore has a localhost attack against it which allows recovery of the encrypted  xlockmore has a localhost attack against it which allows recovery of the encrypted
 hash of the root password.  The damage to systems using DES passwords from this  hash of the root password.  The damage to systems using DES passwords from this
Line 126 
Line 124 
 This is the 2nd patch designed to solve this problem.  This is the 2nd patch designed to solve this problem.
 <p>  <p>
 <li id="rzsz">  <li id="rzsz">
 <font color="#009000"><strong>021: RZSZ SNOOPING: Jan 31, 2000</strong></font>  <strong>021: RZSZ SNOOPING: Jan 31, 2000</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 The rzsz port was removed from the ports collection, as it collects and  The rzsz port was removed from the ports collection, as it collects and
 sends user information to a designated email address, effectively spying on  sends user information to a designated email address, effectively spying on
Line 134 
Line 132 
 it</em>.  it</em>.
 <p>  <p>
 <li id="syslog">  <li id="syslog">
 <font color="#009000"><strong>020: LIBRARY IMPROVEMENT: Jan 26, 2000</strong></font>  <strong>020: LIBRARY IMPROVEMENT: Jan 26, 2000</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 syslog(3) would not try to reopen the socket, thus, nightly newsyslog(8)  syslog(3) would not try to reopen the socket, thus, nightly newsyslog(8)
 would cause syslogd(8) to not see new messages.  would cause syslogd(8) to not see new messages.
Line 142 
Line 140 
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
 <li id="nsphy">  <li id="nsphy">
 <font color="#009000"><strong>019: DRIVER IMPROVEMENT: Jan 20, 2000</strong></font>  <strong>019: DRIVER IMPROVEMENT: Jan 20, 2000</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 Intel fxp cards with National Semiconductor PHYs (nsphy) have trouble  Intel fxp cards with National Semiconductor PHYs (nsphy) have trouble
 negotiating and maintaining 100Mb link integrity.<br>  negotiating and maintaining 100Mb link integrity.<br>
Line 150 
Line 148 
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
 <li id="procfs">  <li id="procfs">
 <font color="#009000"><strong>018: SECURITY FIX: Jan 20, 2000</strong></font>  <strong>018: SECURITY FIX: Jan 20, 2000</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 Systems running with procfs enabled and mounted are vulnerable  Systems running with procfs enabled and mounted are vulnerable
 to having the stderr output of setuid processes directed onto  to having the stderr output of setuid processes directed onto
Line 160 
Line 158 
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
 <li id="fortran">  <li id="fortran">
 <font color="#009000"><strong>017: FUNCTIONALITY ADDITION: Nov 14, 1999</strong></font>  <strong>017: FUNCTIONALITY ADDITION: Nov 14, 1999</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 Fortran doesn't work right.  The file /usr/include/g2c.h is missing in the  Fortran doesn't work right.  The file /usr/include/g2c.h is missing in the
 release.<br>  release.<br>
Line 171 
Line 169 
 the include file</a> to your system.  the include file</a> to your system.
 <p>  <p>
 <li id="sslUSA">  <li id="sslUSA">
 <font color="#009000"><strong>016: SECURITY FIX: Dec 2, 1999</strong></font>  <strong>016: SECURITY FIX: Dec 2, 1999</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 A buffer overflow in the RSAREF code included in the  A buffer overflow in the RSAREF code included in the
 USA version of the libssl package (called <strong>sslUSA</strong>, is  USA version of the libssl package (called <b>sslUSA</b>, is
 possibly exploitable in isakmpd if SSL/RSA features  possibly exploitable in isakmpd if SSL/RSA features
 are enabled or used.<br>  are enabled or used.<br>
 <a href="https://www.openssh.com">OpenSSH</a> and httpd (with -DSSL) are not  <a href="https://www.openssh.com">OpenSSH</a> and httpd (with -DSSL) are not
 vulnerable.<br>  vulnerable.<br>
 <strong>NOTE: International users using the ssl26 package are not affected.</strong>  <b>NOTE: International users using the ssl26 package are not affected.</b>
 <p>  <p>
 To check what package you are using, use  To check what package you are using, use
 <pre>  <pre>
Line 189 
Line 187 
 "ssl26.1 USA-only non-commercial crypto libs incl. SSL &amp; RSA"  "ssl26.1 USA-only non-commercial crypto libs incl. SSL &amp; RSA"
 <p>  <p>
 Non-commercial USA users who installed the ssl package before December 3  Non-commercial USA users who installed the ssl package before December 3
 should upgrade their <strong>sslUSA26</strong> package using:<br>  should upgrade their <b>sslUSA26</b> package using:<br>
 <pre>  <pre>
 <b>#</b> pkg_delete sslUSA26  <b>#</b> pkg_delete sslUSA26
 <b>#</b> pkg_add -v sslUSA26.tar.gz  <b>#</b> pkg_add -v sslUSA26.tar.gz
 </pre>  </pre>
 Using the new <strong>sslUSA26.tar.gz</strong> files which have been placed  Using the new <b>sslUSA26.tar.gz</b> files which have been placed
 on the FTP mirrors.<br>  on the FTP mirrors.<br>
 <a href="advisories/sslUSA">For more information, see the advisory</a>.<br>  <a href="advisories/sslUSA">For more information, see the advisory</a>.<br>
 <strong>NOTE: this problem turned out to not be unexploitable in OpenSSH.</strong>  <b>NOTE: this problem turned out to not be unexploitable in OpenSSH.</b>
 <p>  <p>
 <li id="aty2k">  <li id="aty2k">
 <font color="#009000"><strong>015: Y2K FIX: Jan 9, 2000</strong></font>  <strong>015: Y2K FIX: Jan 9, 2000</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 The at(1) command was unable to parse some kinds of dates.<br>  The at(1) command was unable to parse some kinds of dates.<br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/015_aty2k.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/015_aty2k.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
 <li id="eepromy2k">  <li id="eepromy2k">
 <font color="#009000"><strong>014: Y2K FIX: Jan 3, 2000</strong></font><br>  <strong>014: Y2K FIX: Jan 3, 2000</strong><br>
 A minor problem; the sparc eeprom(8) command is not Y2K compliant.<br>  A minor problem; the sparc eeprom(8) command is not Y2K compliant.<br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.6/sparc/014_eepromy2k.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.6/sparc/014_eepromy2k.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 This is the second revision of the patch.  This is the second revision of the patch.
 <p>  <p>
 <li id="addusery2k">  <li id="addusery2k">
 <font color="#009000"><strong>013: Y2K FIX: Jan 3, 2000</strong></font>  <strong>013: Y2K FIX: Jan 3, 2000</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 A minor problem in the logging support for the adduser(8) command.<br>  A minor problem in the logging support for the adduser(8) command.<br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/013_addusery2k.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/013_addusery2k.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
 <li id="packets3c900b">  <li id="packets3c900b">
 <font color="#009000"><strong>012: DRIVER IMPROVEMENT: Jan 3, 2000</strong></font>  <strong>012: DRIVER IMPROVEMENT: Jan 3, 2000</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 The 3C900B-TPO fails to select the correct media type (it never sees or  The 3C900B-TPO fails to select the correct media type (it never sees or
 sends packets).<br>  sends packets).<br>
Line 229 
Line 227 
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
 <li id="poll">  <li id="poll">
 <font color="#009000"><strong>011: SECURITY FIX: Dec 4, 1999</strong></font>  <strong>011: SECURITY FIX: Dec 4, 1999</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 Various bugs in poll(2) may cause a kernel crash.<br>  Various bugs in poll(2) may cause a kernel crash.<br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/011_poll.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/011_poll.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
 <li id="sendmail">  <li id="sendmail">
 <font color="#009000"><strong>010: SECURITY FIX: Dec 4, 1999</strong></font>  <strong>010: SECURITY FIX: Dec 4, 1999</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 Sendmail had a race in aliases file handling, which this patch fixes.<br>  Sendmail had a race in aliases file handling, which this patch fixes.<br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/010_sendmail.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/010_sendmail.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
 <li id="atapijumbo">  <li id="atapijumbo">
 <font color="#009000"><strong>009: DRIVER IMPROVEMENTS: Dec 4, 1999</strong></font>  <strong>009: DRIVER IMPROVEMENTS: Dec 4, 1999</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 Various improvements have been made to the IDE/ATAPI subsystem since  Various improvements have been made to the IDE/ATAPI subsystem since
 the 2.6 release shipped.<br>  the 2.6 release shipped.<br>
Line 252 
Line 250 
 Revision 1 of this jumbo source code patch exists.</a><br>  Revision 1 of this jumbo source code patch exists.</a><br>
 <p>  <p>
 <li id="hp300_locore">  <li id="hp300_locore">
 <font color="#009000"><strong>007: RELIABILITY FIX: Nov 12, 1999</strong></font>  <strong>007: RELIABILITY FIX: Nov 12, 1999</strong>
 &nbsp; <i>m68k architectures</i><br>  &nbsp; <i>m68k architectures</i><br>
 All m68k kernels can possibly be crashed by a user.<br>  All m68k kernels can possibly be crashed by a user.<br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.6/m68k/007_locore.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.6/m68k/007_locore.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
 <li id="alpha_locore">  <li id="alpha_locore">
 <font color="#009000"><strong>006: RELIABILITY FIX: Nov 13, 1999</strong></font>  <strong>006: RELIABILITY FIX: Nov 13, 1999</strong>
 &nbsp; <i>alpha only</i><br>  &nbsp; <i>alpha only</i><br>
 The alpha kernel can possibly be crashed by a user.<br>  The alpha kernel can possibly be crashed by a user.<br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.6/alpha/006_locore.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.6/alpha/006_locore.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
 <li id="sshjumbo">  <li id="sshjumbo">
 <font color="#009000"><strong>005: FUNCTIONALITY ADDITION: Nov 11, 1999</strong></font>  <strong>005: FUNCTIONALITY ADDITION: Nov 11, 1999</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 Various OpenSSH improvements have been made since the 2.6 release shipped.<br>  Various OpenSSH improvements have been made since the 2.6 release shipped.<br>
 To resolve the various (non-security related) features which users may want,  To resolve the various (non-security related) features which users may want,
 we are making a jumbo patch available.  <strong>This is now at VERSION FOUR.</strong><br>  we are making a jumbo patch available.  <b>This is now at VERSION FOUR.</b><br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/005_sshjumbo.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/005_sshjumbo.patch">
 Revision 4 of this jumbo source code patch exists.</a><br>  Revision 4 of this jumbo source code patch exists.</a><br>
 <strong>NOTE: /etc/sshd_config and /etc/ssh_config may need changes.</strong>  <b>NOTE: /etc/sshd_config and /etc/ssh_config may need changes.</b>
 <p>  <p>
 <li id="sparc_locore">  <li id="sparc_locore">
 <font color="#009000"><strong>004: RELIABILITY FIX: Nov 12, 1999</strong></font>  <strong>004: RELIABILITY FIX: Nov 12, 1999</strong>
 &nbsp; <i>sparc only</i><br>  &nbsp; <i>sparc only</i><br>
 The sparc kernel can be crashed by a user.<br>  The sparc kernel can be crashed by a user.<br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.6/sparc/004_locore.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.6/sparc/004_locore.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
 <li id="m4">  <li id="m4">
 <font color="#009000"><strong>003: FUNCTIONALITY FIX: Nov 10, 1999</strong></font>  <strong>003: FUNCTIONALITY FIX: Nov 10, 1999</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 m4 is quite broken in the 2.6 release.<br>  m4 is quite broken in the 2.6 release.<br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/003_m4.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/003_m4.patch">
Line 291 
Line 289 
 This is the 3rd revision of the patch.  This is the 3rd revision of the patch.
 <p>  <p>
 <li id="ifmedia">  <li id="ifmedia">
 <font color="#009000"><strong>002: SECURITY FIX: Nov 9, 1999</strong></font>  <strong>002: SECURITY FIX: Nov 9, 1999</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 Any user can change interface media configurations.<br>  Any user can change interface media configurations.<br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/002_ifmedia.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/002_ifmedia.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
 <li id="newsyslog">  <li id="newsyslog">
 <font color="#009000"><strong>001: RELIABILITY FIX: Nov 8, 1999</strong></font>  <strong>001: RELIABILITY FIX: Nov 8, 1999</strong>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 A race condition in newsyslog(8) can cause errors in log file rotation.<br>  A race condition in newsyslog(8) can cause errors in log file rotation.<br>
 <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/001_newsyslog.patch">  <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/001_newsyslog.patch">
Line 308 
Line 306 
 </ul>  </ul>
   
 <hr>  <hr>
   
 </body>  
 </html>  
Legend:
Removed from v.1.84  
changed lines
  Added in v.1.85