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

Diff for /www/errata25.html between version 1.59 and 1.60

version 1.59, 2014/10/02 14:34:45 version 1.60, 2015/02/14 04:36:51
Line 81 
Line 81 
 <hr>  <hr>
   
 <ul>  <ul>
 <li><a name="cron"></a>  <li id="cron">
 <font color="#009000"><strong>SECURITY FIX: Aug 30, 1999</strong></font>  <font color="#009000"><strong>SECURITY FIX: Aug 30, 1999</strong></font>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 In cron(8), make sure argv[] is NULL terminated in the fake popen() and  In cron(8), make sure argv[] is NULL terminated in the fake popen() and
Line 89 
Line 89 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.5/common/012_cron.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.5/common/012_cron.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="miscfs"></a>  <li id="miscfs">
 <font color="#009000"><strong>SECURITY FIX: Aug 12, 1999</strong></font>  <font color="#009000"><strong>SECURITY FIX: Aug 12, 1999</strong></font>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 The procfs and fdescfs filesystems had an overrun in their handling  The procfs and fdescfs filesystems had an overrun in their handling
Line 98 
Line 98 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.5/common/011_miscfs.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.5/common/011_miscfs.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="profil"></a>  <li id="profil">
 <font color="#009000"><strong>SECURITY FIX: Aug 9, 1999</strong></font>  <font color="#009000"><strong>SECURITY FIX: Aug 9, 1999</strong></font>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 Stop profiling (see profil(2)) when we execve() a new process.  Stop profiling (see profil(2)) when we execve() a new process.
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.5/common/010_profil.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.5/common/010_profil.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="ipsec_in_use"></a>  <li id="ipsec_in_use">
 <font color="#009000"><strong>SECURITY FIX: Aug 6, 1999</strong></font>  <font color="#009000"><strong>SECURITY FIX: Aug 6, 1999</strong></font>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 Packets that should have been handled by IPsec may be transmitted  Packets that should have been handled by IPsec may be transmitted
Line 113 
Line 113 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.5/common/009_ipsec_in_use.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.5/common/009_ipsec_in_use.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="rc"></a>  <li id="rc">
 <font color="#009000"><strong>SECURITY FIX: Aug 5, 1999</strong></font>  <font color="#009000"><strong>SECURITY FIX: Aug 5, 1999</strong></font>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 In /etc/rc, use mktemp(1) for motd re-writing, and change the find(1)  In /etc/rc, use mktemp(1) for motd re-writing, and change the find(1)
Line 121 
Line 121 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.5/common/008_rc.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.5/common/008_rc.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="chflags"></a>  <li id="chflags">
 <font color="#009000"><strong>SECURITY FIX: Jul 30, 1999</strong></font>  <font color="#009000"><strong>SECURITY FIX: Jul 30, 1999</strong></font>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 Do not permit regular users to chflags(2) or fchflags(2) on character or  Do not permit regular users to chflags(2) or fchflags(2) on character or
Line 129 
Line 129 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.5/common/007_chflags.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.5/common/007_chflags.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="nroff"></a>  <li id="nroff">
 <font color="#009000"><strong>SECURITY FIX: Jul 27, 1999</strong></font>  <font color="#009000"><strong>SECURITY FIX: Jul 27, 1999</strong></font>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 Cause groff(1) to be invoked with the -S flag, when called by nroff(1),  Cause groff(1) to be invoked with the -S flag, when called by nroff(1),
Line 139 
Line 139 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.5/common/006_nroff.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.5/common/006_nroff.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="fts"></a>  <li id="fts">
 <font color="#009000"><strong>RELIABILITY FIX: May 19, 1999</strong></font>  <font color="#009000"><strong>RELIABILITY FIX: May 19, 1999</strong></font>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 Programs using fts(3) could dump core when given a directory structure  Programs using fts(3) could dump core when given a directory structure
Line 147 
Line 147 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.5/common/005_fts.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.5/common/005_fts.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="tcpsack"></a>  <li id="tcpsack">
 <font color="#009000"><strong>RELIABILITY FIX: May 19, 1999</strong></font>  <font color="#009000"><strong>RELIABILITY FIX: May 19, 1999</strong></font>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 Sequence numbers could wrap with TCP_SACK and TCP_NEWRENO, resulting in  Sequence numbers could wrap with TCP_SACK and TCP_NEWRENO, resulting in
Line 155 
Line 155 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.5/common/004_tcpsack.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.5/common/004_tcpsack.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="ipsec1"></a>  <li id="ipsec1">
 <font color="#009000"><strong>RELIABILITY FIX</strong></font>  <font color="#009000"><strong>RELIABILITY FIX</strong></font>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 Retransmitted TCP packets could get corrupted when flowing over an  Retransmitted TCP packets could get corrupted when flowing over an
Line 163 
Line 163 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.5/common/003_espdata.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.5/common/003_espdata.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="bmap"></a>  <li id="bmap">
 <font color="#009000"><strong>RELIABILITY FIX</strong></font>  <font color="#009000"><strong>RELIABILITY FIX</strong></font>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 A local user can crash the system by reading a file larger than 64meg  A local user can crash the system by reading a file larger than 64meg
Line 171 
Line 171 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.5/common/002_bmap.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.5/common/002_bmap.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="pfkey"></a>  <li id="pfkey">
 <font color="#009000"><strong>RELIABILITY FIX</strong></font>  <font color="#009000"><strong>RELIABILITY FIX</strong></font>
 &nbsp; <i>All architectures</i><br>  &nbsp; <i>All architectures</i><br>
 PF_KEY socket operations leak internal kernel resources, so that a  PF_KEY socket operations leak internal kernel resources, so that a
Line 181 
Line 181 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.5/common/001_pfkey.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.5/common/001_pfkey.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="y2k"></a>  <li id="y2k">
 <font color="#009000"><strong>Y2K FIX: Aug 30, 1999</strong></font><br>  <font color="#009000"><strong>Y2K FIX: Aug 30, 1999</strong></font><br>
 This patch corrects various OpenBSD/i386 2.5 problems with Y2K. The 2.6  This patch corrects various OpenBSD/i386 2.5 problems with Y2K. The 2.6
 release (released at 1 Dec 1999) has this problem solved. This patch is  release (released at 1 Dec 1999) has this problem solved. This patch is
Line 189 
Line 189 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.5/i386/014_y2k.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.5/i386/014_y2k.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="brooktree"></a>  <li id="brooktree">
 <font color="#009000"><strong>RELIABILITY FIX</strong></font><br>  <font color="#009000"><strong>RELIABILITY FIX</strong></font><br>
 If a user opened the brooktree device on a system where it did not exist,  If a user opened the brooktree device on a system where it did not exist,
 the kernel crashed.  the kernel crashed.
 <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.5/i386/013_brooktree.patch">  <a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.5/i386/013_brooktree.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="macutils"></a>  <li id="macutils">
 <font color="#009000"><strong>INSTALL PROBLEM</strong></font><br>  <font color="#009000"><strong>INSTALL PROBLEM</strong></font><br>
 The mac68k install utils were mistakenly left off the CD and out of  The mac68k install utils were mistakenly left off the CD and out of
 the FTP install directories.  These tools have now been added to the  the FTP install directories.  These tools have now been added to the
Line 204 
Line 204 
 <a href="http://ftp.openbsd.org/pub/OpenBSD/2.5/mac68k/utils">  <a href="http://ftp.openbsd.org/pub/OpenBSD/2.5/mac68k/utils">
 http://ftp.openbsd.org/pub/OpenBSD/2.5/mac68k/utils</a>  http://ftp.openbsd.org/pub/OpenBSD/2.5/mac68k/utils</a>
 <p>  <p>
 <li><a name="powerpc_trap"></a>  <li id="powerpc_trap">
 <font color="#009000"><strong>RELIABILITY FIX</strong></font><br>  <font color="#009000"><strong>RELIABILITY FIX</strong></font><br>
 Two problems in the powerpc kernel trap handling cause severe system  Two problems in the powerpc kernel trap handling cause severe system
 unreliability.  unreliability.
Legend:
Removed from v.1.59  
changed lines
  Added in v.1.60