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

Diff for /www/errata26.html between version 1.44 and 1.45

version 1.44, 2010/03/08 21:53:37 version 1.45, 2010/07/08 19:00:07
Line 53 
Line 53 
 <br>  <br>
 <hr>  <hr>
   
 <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6.tar.gz">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.6.tar.gz">
 You can also fetch a tar.gz file containing all the following patches</a>.  You can also fetch a tar.gz file containing all the following patches</a>.
 This file is updated once a day.  This file is updated once a day.
   
Line 72 
Line 72 
 used as a local denial of service attack which would block the exiting of  used as a local denial of service attack which would block the exiting of
 processes which had semaphore resources allocated. Processes not using  processes which had semaphore resources allocated. Processes not using
 semaphores are not affected, so the actual effect is very minimal.<br>  semaphores are not affected, so the actual effect is very minimal.<br>
 <a href="ftp://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 jumbo patch exists which remedies this problem.</a>  A jumbo patch exists which remedies this problem.</a>
 <p>  <p>
 <li><a name="ipf"></a>  <li><a name="ipf"></a>
Line 82 
Line 82 
 bypassed.  bypassed.
 This patch also includes fixes for an unaligned timestamp issue,  This patch also includes fixes for an unaligned timestamp issue,
 and reliability fixes for ipmon and the in-kernel ftp proxy.<br>  and reliability fixes for ipmon and the in-kernel ftp proxy.<br>
 <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/023_ipf.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/023_ipf.patch">
 A jumbo patch exists</a>, which remedies this problem, and updates ipf  A jumbo patch exists</a>, which remedies this problem, and updates ipf
 to version 3.3.16.  to version 3.3.16.
 <p>  <p>
Line 97 
Line 97 
 the impact is much reduced.<br>  the impact is much reduced.<br>
 (Aside:  We do not consider this a localhost root hole in the default install,  (Aside:  We do not consider this a localhost root hole in the default install,
 since we have not seen a fast blowfish cracker yet ;-)<br>  since we have not seen a fast blowfish cracker yet ;-)<br>
 <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/022_xlockmore.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/022_xlockmore.patch">
 A source code patch exists, which remedies this problem. This is the 2nd patch designed to solve this problem.</a>  A source code patch exists, which remedies this problem. This is the 2nd patch designed to solve this problem.</a>
 <p>  <p>
 <li><a name="rzsz"></a>  <li><a name="rzsz"></a>
Line 111 
Line 111 
 <font color="#009000"><strong>020: LIBRARY IMPROVEMENT: Jan 26, 2000</strong></font><br>  <font color="#009000"><strong>020: LIBRARY IMPROVEMENT: Jan 26, 2000</strong></font><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.
 <a href="ftp://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><a name="nsphy"></a>
 <font color="#009000"><strong>019: DRIVER IMPROVEMENT: Jan 20, 2000</strong></font><br>  <font color="#009000"><strong>019: DRIVER IMPROVEMENT: Jan 20, 2000</strong></font><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>
 <a href="ftp://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><a name="procfs"></a>
Line 127 
Line 127 
 to having the stderr output of setuid processes directed onto  to having the stderr output of setuid processes directed onto
 a pre-seeked descriptor onto the stack in their own procfs memory.<br>  a pre-seeked descriptor onto the stack in their own procfs memory.<br>
 Note that procfs is not mounted by default in OpenBSD.<br>  Note that procfs is not mounted by default in OpenBSD.<br>
 <a href="ftp://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="aty2k"></a>  <li><a name="aty2k"></a>
 <font color="#009000"><strong>015: Y2K FIX: Jan 9, 2000</strong></font><br>  <font color="#009000"><strong>015: Y2K FIX: Jan 9, 2000</strong></font><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="ftp://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="addusery2k"></a>  <li><a name="addusery2k"></a>
 <font color="#009000"><strong>013: Y2K FIX: Jan 3, 2000</strong></font><br>  <font color="#009000"><strong>013: Y2K FIX: Jan 3, 2000</strong></font><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="ftp://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><a name="3c900b"></a>
 <font color="#009000"><strong>012: DRIVER IMPROVEMENT: Jan 3, 2000</strong></font><br>  <font color="#009000"><strong>012: DRIVER IMPROVEMENT: Jan 3, 2000</strong></font><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>
 <a href="ftp://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><a name="poll"></a>
 <font color="#009000"><strong>011: SECURITY FIX: Dec 4, 1999</strong></font><br>  <font color="#009000"><strong>011: SECURITY FIX: Dec 4, 1999</strong></font><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="ftp://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><a name="sendmail"></a>
 <font color="#009000"><strong>010: SECURITY FIX: Dec 4, 1999</strong></font><br>  <font color="#009000"><strong>010: SECURITY FIX: Dec 4, 1999</strong></font><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="ftp://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><a name="atapijumbo"></a>
Line 166 
Line 166 
 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>
 Some of these improvements make some recalcitrant devices work much better.  Some of these improvements make some recalcitrant devices work much better.
 <a href="ftp://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="sslUSA"></a>  <li><a name="sslUSA"></a>
Line 201 
Line 201 
 <font color="#009000"><strong>017: FUNCTIONALITY ADDITION: Nov 14, 1999</strong></font><br>  <font color="#009000"><strong>017: FUNCTIONALITY ADDITION: Nov 14, 1999</strong></font><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>
 <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/008_fortran.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/008_fortran.patch">
 A source code patch exists which remedies this problem.</a><br>  A source code patch exists which remedies this problem.</a><br>
 The patch fixes the source tree and describes how to properly add  The patch fixes the source tree and describes how to properly add
 <a href="ftp://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="sshjumbo"></a>  <li><a name="sshjumbo"></a>
Line 212 
Line 212 
 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.  <strong>This is now at VERSION FOUR.</strong><br>
 <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/005_sshjumbo.patch">  <a href="http://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>  <strong>NOTE: /etc/sshd_config and /etc/ssh_config may need changes.</strong>
 <p>  <p>
 <li><a name="m4"></a>  <li><a name="m4"></a>
 <font color="#009000"><strong>003: FUNCTIONALITY FIX: Nov 10, 1999</strong></font><br>  <font color="#009000"><strong>003: FUNCTIONALITY FIX: Nov 10, 1999</strong></font><br>
 m4 is quite broken in the 2.6 release.<br>  m4 is quite broken in the 2.6 release.<br>
 <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/003_m4.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/003_m4.patch">
 The 3rd version of the source code patch exists, which remedies this problem.</a>  The 3rd version of the source code patch exists, which remedies this problem.</a>
 <p>  <p>
 <li><a name="ifmedia"></a>  <li><a name="ifmedia"></a>
 <font color="#009000"><strong>002: SECURITY FIX: Nov 9, 1999</strong></font><br>  <font color="#009000"><strong>002: SECURITY FIX: Nov 9, 1999</strong></font><br>
 Any user can change interface media configurations.<br>  Any user can change interface media configurations.<br>
 <a href="ftp://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><a name="newsyslog"></a>
 <font color="#009000"><strong>001: RELIABILITY FIX: Nov 8, 1999</strong></font><br>  <font color="#009000"><strong>001: RELIABILITY FIX: Nov 8, 1999</strong></font><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="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/001_newsyslog.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/001_newsyslog.patch">
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
 </ul>  </ul>
Line 249 
Line 249 
 <a name="mac68k_locore"></a>  <a name="mac68k_locore"></a>
 <font color="#009000"><strong>007: RELIABILITY FIX: Nov 12, 1999</strong></font><br>  <font color="#009000"><strong>007: RELIABILITY FIX: Nov 12, 1999</strong></font><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="ftp://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>
 </ul>  </ul>
Line 260 
Line 260 
 <li><a name="eepromy2k"></a>  <li><a name="eepromy2k"></a>
 <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="ftp://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">
 Revision 2 of the source code patch exists, which remedies this problem.</a>  Revision 2 of the source code patch exists, which remedies this problem.</a>
 <p>  <p>
 <li><a name="sparc_locore"></a>  <li><a name="sparc_locore"></a>
 <font color="#009000"><strong>004: RELIABILITY FIX: Nov 12, 1999</strong></font><br>  <font color="#009000"><strong>004: RELIABILITY FIX: Nov 12, 1999</strong></font><br>
 The sparc kernel can be crashed by a user.<br>  The sparc kernel can be crashed by a user.<br>
 <a href="ftp://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>
 </ul>  </ul>
Line 277 
Line 277 
 <li><a name="amiga_locore"></a>  <li><a name="amiga_locore"></a>
 <font color="#009000"><strong>007: RELIABILITY FIX: Nov 12, 1999</strong></font><br>  <font color="#009000"><strong>007: RELIABILITY FIX: Nov 12, 1999</strong></font><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="ftp://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>
 </ul>  </ul>
Line 300 
Line 300 
 <li><a name="alpha_locore"></a>  <li><a name="alpha_locore"></a>
 <font color="#009000"><strong>006: RELIABILITY FIX: Nov 13, 1999</strong></font><br>  <font color="#009000"><strong>006: RELIABILITY FIX: Nov 13, 1999</strong></font><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="ftp://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>
 </ul>  </ul>
Line 311 
Line 311 
 <li><a name="hp300_locore"></a>  <li><a name="hp300_locore"></a>
 <font color="#009000"><strong>007: RELIABILITY FIX: Nov 12, 1999</strong></font><br>  <font color="#009000"><strong>007: RELIABILITY FIX: Nov 12, 1999</strong></font><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="ftp://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>
 </ul>  </ul>
Line 322 
Line 322 
 <li><a name="mvme68k_locore"></a>  <li><a name="mvme68k_locore"></a>
 <font color="#009000"><strong>007: RELIABILITY FIX: Nov 12, 1999</strong></font><br>  <font color="#009000"><strong>007: RELIABILITY FIX: Nov 12, 1999</strong></font><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="ftp://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>
 </ul>  </ul>
Legend:
Removed from v.1.44  
changed lines
  Added in v.1.45