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

Diff for /www/errata26.html between version 1.62 and 1.63

version 1.62, 2014/10/02 14:34:45 version 1.63, 2015/02/14 04:36:51
Line 81 
Line 81 
 <hr>  <hr>
   
 <ul>  <ul>
 <li><a name="semconfig"></a>  <li id="semconfig">
 <font color="#009000"><strong>024: SECURITY FIX: May 26, 2000</strong></font>  <font color="#009000"><strong>024: SECURITY FIX: May 26, 2000</strong></font>
 &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
Line 92 
Line 92 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/024_sysv_sem.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/024_sysv_sem.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
 <li><a name="ipf"></a>  <li id="ipf">
 <font color="#009000"><strong>023: SECURITY FIX: May 25, 2000</strong></font>  <font color="#009000"><strong>023: SECURITY FIX: May 25, 2000</strong></font>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 A misuse of ipf(8)  A misuse of ipf(8)
Line 104 
Line 104 
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 It updates ipf to version 3.3.16.  It updates ipf to version 3.3.16.
 <p>  <p>
 <li><a name="xlockmore"></a>  <li id="xlockmore">
 <font color="#009000"><strong>022: SECURITY FIX: May 25, 2000</strong></font>  <font color="#009000"><strong>022: SECURITY FIX: May 25, 2000</strong></font>
 &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
Line 120 
Line 120 
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 This is the 2nd patch designed to solve this problem.  This is the 2nd patch designed to solve this problem.
 <p>  <p>
 <li><a name="rzsz"></a>  <li id="rzsz">
 <font color="#009000"><strong>021: RZSZ SNOOPING: Jan 31, 2000</strong></font>  <font color="#009000"><strong>021: RZSZ SNOOPING: Jan 31, 2000</strong></font>
 &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
Line 128 
Line 128 
 you.  <em>It is recommended that you remove this package if you installed  you.  <em>It is recommended that you remove this package if you installed
 it</em>.  it</em>.
 <p>  <p>
 <li><a name="syslog"></a>  <li id="syslog">
 <font color="#009000"><strong>020: LIBRARY IMPROVEMENT: Jan 26, 2000</strong></font>  <font color="#009000"><strong>020: LIBRARY IMPROVEMENT: Jan 26, 2000</strong></font>
 &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)
Line 136 
Line 136 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/020_syslog.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/020_syslog.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
 <li><a name="nsphy"></a>  <li id="nsphy">
 <font color="#009000"><strong>019: DRIVER IMPROVEMENT: Jan 20, 2000</strong></font>  <font color="#009000"><strong>019: DRIVER IMPROVEMENT: Jan 20, 2000</strong></font>
 &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
Line 144 
Line 144 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/019_nsphy.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/019_nsphy.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
 <li><a name="procfs"></a>  <li id="procfs">
 <font color="#009000"><strong>018: SECURITY FIX: Jan 20, 2000</strong></font>  <font color="#009000"><strong>018: SECURITY FIX: Jan 20, 2000</strong></font>
 &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
Line 154 
Line 154 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/018_procfs.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/018_procfs.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
 <li><a name="fortran"></a>  <li id="fortran">
 <font color="#009000"><strong>017: FUNCTIONALITY ADDITION: Nov 14, 1999</strong></font>  <font color="#009000"><strong>017: FUNCTIONALITY ADDITION: Nov 14, 1999</strong></font>
 &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
Line 165 
Line 165 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/g2c.h">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/g2c.h">
 the include file</a> to your system.  the include file</a> to your system.
 <p>  <p>
 <li><a name="sslUSA"></a>  <li id="sslUSA">
 <font color="#009000"><strong>016: SECURITY FIX: Dec 2, 1999</strong></font>  <font color="#009000"><strong>016: SECURITY FIX: Dec 2, 1999</strong></font>
 &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
Line 194 
Line 194 
 <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>  <strong>NOTE: this problem turned out to not be unexploitable in OpenSSH.</strong>
 <p>  <p>
 <li><a name="aty2k"></a>  <li id="aty2k">
 <font color="#009000"><strong>015: Y2K FIX: Jan 9, 2000</strong></font>  <font color="#009000"><strong>015: Y2K FIX: Jan 9, 2000</strong></font>
 &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="http://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/015_aty2k.patch">  <a href="http://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><a name="eepromy2k"></a>  <li id="eepromy2k">
 <font color="#009000"><strong>014: Y2K FIX: Jan 3, 2000</strong></font><br>  <font color="#009000"><strong>014: Y2K FIX: Jan 3, 2000</strong></font><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="http://ftp.openbsd.org/pub/OpenBSD/patches/2.6/sparc/014_eepromy2k.patch">  <a href="http://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><a name="addusery2k"></a>  <li id="addusery2k">
 <font color="#009000"><strong>013: Y2K FIX: Jan 3, 2000</strong></font>  <font color="#009000"><strong>013: Y2K FIX: Jan 3, 2000</strong></font>
 &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="http://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/013_addusery2k.patch">  <a href="http://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><a name="3c900b"></a>  <li id="3c900b">
 <font color="#009000"><strong>012: DRIVER IMPROVEMENT: Jan 3, 2000</strong></font>  <font color="#009000"><strong>012: DRIVER IMPROVEMENT: Jan 3, 2000</strong></font>
 &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
Line 223 
Line 223 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/012_3c900b.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/012_3c900b.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
 <li><a name="poll"></a>  <li id="poll">
 <font color="#009000"><strong>011: SECURITY FIX: Dec 4, 1999</strong></font>  <font color="#009000"><strong>011: SECURITY FIX: Dec 4, 1999</strong></font>
 &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="http://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/011_poll.patch">  <a href="http://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><a name="sendmail"></a>  <li id="sendmail">
 <font color="#009000"><strong>010: SECURITY FIX: Dec 4, 1999</strong></font>  <font color="#009000"><strong>010: SECURITY FIX: Dec 4, 1999</strong></font>
 &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="http://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/010_sendmail.patch">  <a href="http://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><a name="atapijumbo"></a>  <li id="atapijumbo">
 <font color="#009000"><strong>009: DRIVER IMPROVEMENTS: Dec 4, 1999</strong></font>  <font color="#009000"><strong>009: DRIVER IMPROVEMENTS: Dec 4, 1999</strong></font>
 &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
Line 246 
Line 246 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/009_atapi.patch"><br>  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/009_atapi.patch"><br>
 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><a name="hp300_locore"></a>  <li id="hp300_locore">
 <font color="#009000"><strong>007: RELIABILITY FIX: Nov 12, 1999</strong></font>  <font color="#009000"><strong>007: RELIABILITY FIX: Nov 12, 1999</strong></font>
 &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="http://ftp.openbsd.org/pub/OpenBSD/patches/2.6/m68k/007_locore.patch">  <a href="http://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><a name="alpha_locore"></a>  <li id="alpha_locore">
 <font color="#009000"><strong>006: RELIABILITY FIX: Nov 13, 1999</strong></font>  <font color="#009000"><strong>006: RELIABILITY FIX: Nov 13, 1999</strong></font>
 &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="http://ftp.openbsd.org/pub/OpenBSD/patches/2.6/alpha/006_locore.patch">  <a href="http://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><a name="sshjumbo"></a>  <li id="sshjumbo">
 <font color="#009000"><strong>005: FUNCTIONALITY ADDITION: Nov 11, 1999</strong></font>  <font color="#009000"><strong>005: FUNCTIONALITY ADDITION: Nov 11, 1999</strong></font>
 &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>
Line 270 
Line 270 
 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>  <strong>NOTE: /etc/sshd_config and /etc/ssh_config may need changes.</strong>
 <p>  <p>
 <li><a name="sparc_locore"></a>  <li id="sparc_locore">
 <font color="#009000"><strong>004: RELIABILITY FIX: Nov 12, 1999</strong></font>  <font color="#009000"><strong>004: RELIABILITY FIX: Nov 12, 1999</strong></font>
 &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="http://ftp.openbsd.org/pub/OpenBSD/patches/2.6/sparc/004_locore.patch">  <a href="http://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><a name="m4"></a>  <li id="m4">
 <font color="#009000"><strong>003: FUNCTIONALITY FIX: Nov 10, 1999</strong></font>  <font color="#009000"><strong>003: FUNCTIONALITY FIX: Nov 10, 1999</strong></font>
 &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>
Line 285 
Line 285 
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 This is the 3rd revision of the patch.  This is the 3rd revision of the patch.
 <p>  <p>
 <li><a name="ifmedia"></a>  <li id="ifmedia">
 <font color="#009000"><strong>002: SECURITY FIX: Nov 9, 1999</strong></font>  <font color="#009000"><strong>002: SECURITY FIX: Nov 9, 1999</strong></font>
 &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="http://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/002_ifmedia.patch">  <a href="http://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><a name="newsyslog"></a>  <li id="newsyslog">
 <font color="#009000"><strong>001: RELIABILITY FIX: Nov 8, 1999</strong></font>  <font color="#009000"><strong>001: RELIABILITY FIX: Nov 8, 1999</strong></font>
 &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>
Legend:
Removed from v.1.62  
changed lines
  Added in v.1.63