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

Diff for /www/errata.html between version 1.202 and 1.203

version 1.202, 1999/11/13 21:51:55 version 1.203, 1999/11/14 09:52:38
Line 36 
Line 36 
 <a name=all></a>  <a name=all></a>
 <li><h3><font color=#e00000>All architectures</font></h3>  <li><h3><font color=#e00000>All architectures</font></h3>
 <ul>  <ul>
   <a name=fortran></a>
   <li><font color=#009000><strong>FUNCTIONALITY ADDITION: Nov 14, 1999</strong></font><br>
   Fortran doesn't work right.  The file /usr/include/g2c.h is missing in the
   release.<br>
   <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/008_fortran.patch>
   A source code patch exists which remedies this problem.</a><br>
   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>
   the include file</a> to your system.
   <p>
 <a name=sshjumbo></a>  <a name=sshjumbo></a>
 <li><font color=#009000><strong>FUNCTIONALITY ADDITION: Nov 10, 1999</strong></font><br>  <li><font color=#009000><strong>FUNCTIONALITY ADDITION: Nov 11, 1999</strong></font><br>
 Various OpenSSH improvements have been made since the 2.6 release shipped.  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, we  To resolve the various (non-security related) features which users may want,
 are making a jumbo patch available.  we are making a jumbo patch available.<br>
 <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/005_sshjumbo.patch>  <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/005_sshjumbo.patch>
 Revision 1 of this jumbo source code patch exists.</a><br>  Revision 1 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>
 <a name=m4></a>  <a name=m4></a>
 <li><font color=#009000><strong>FUNCTIONALITY FIX: Nov 10, 1999</strong></font><br>  <li><font color=#009000><strong>FUNCTIONALITY FIX: Nov 10, 1999</strong></font><br>
 m4 is quite broken in the 2.6 release.  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=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.6/common/003_m4.patch>
 A source code patch exists which remedies this problem.</a>  A source code patch exists which remedies this problem.</a>
 <p>  <p>
 <a name=ifmedia></a>  <a name=ifmedia></a>
 <li><font color=#009000><strong>SECURITY FIX: Nov 9, 1999</strong></font><br>  <li><font color=#009000><strong>SECURITY FIX: Nov 9, 1999</strong></font><br>
 Any user can change interface media configurations.  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=ftp://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>
 <a name=newsyslog></a>  <a name=newsyslog></a>
 <li><font color=#009000><strong>RELIABILITY FIX: Nov 8, 1999</strong></font><br>  <li><font color=#009000><strong>RELIABILITY FIX: Nov 8, 1999</strong></font><br>
 A race condition in newsyslog(8) can cause errors in log file rotation.  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=ftp://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>
Line 77 
Line 87 
 <a name=m68k_locore></a>  <a name=m68k_locore></a>
 <a name=mac68k_locore></a>  <a name=mac68k_locore></a>
 <li><font color=#009000><strong>RELIABILITY FIX: Nov 12, 1999</strong></font><br>  <li><font color=#009000><strong>RELIABILITY FIX: Nov 12, 1999</strong></font><br>
 All m68k kernels can possibly be crashed by a user.  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=ftp://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>
Line 88 
Line 98 
 <ul>  <ul>
 <a name=sparc_locore></a>  <a name=sparc_locore></a>
 <li><font color=#009000><strong>RELIABILITY FIX: Nov 12, 1999</strong></font><br>  <li><font color=#009000><strong>RELIABILITY FIX: Nov 12, 1999</strong></font><br>
 The sparc kernel can be crashed by a user.  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=ftp://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>
Line 99 
Line 109 
 <ul>  <ul>
 <a name=amiga_locore></a>  <a name=amiga_locore></a>
 <li><font color=#009000><strong>RELIABILITY FIX: Nov 12, 1999</strong></font><br>  <li><font color=#009000><strong>RELIABILITY FIX: Nov 12, 1999</strong></font><br>
 All m68k kernels can possibly be crashed by a user.  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=ftp://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>
Line 122 
Line 132 
 <ul>  <ul>
 <a name=alpha_locore></a>  <a name=alpha_locore></a>
 <li><font color=#009000><strong>RELIABILITY FIX: Nov 13, 1999</strong></font><br>  <li><font color=#009000><strong>RELIABILITY FIX: Nov 13, 1999</strong></font><br>
 The alpha kernel can possibly be crashed by a user.  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=ftp://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>
Line 133 
Line 143 
 <ul>  <ul>
 <a name=hp300_locore></a>  <a name=hp300_locore></a>
 <li><font color=#009000><strong>RELIABILITY FIX: Nov 12, 1999</strong></font><br>  <li><font color=#009000><strong>RELIABILITY FIX: Nov 12, 1999</strong></font><br>
 All m68k kernels can possibly be crashed by a user.  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=ftp://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>
Line 144 
Line 154 
 <ul>  <ul>
 <a name=mvme68k_locore></a>  <a name=mvme68k_locore></a>
 <li><font color=#009000><strong>RELIABILITY FIX: Nov 12, 1999</strong></font><br>  <li><font color=#009000><strong>RELIABILITY FIX: Nov 12, 1999</strong></font><br>
 All m68k kernels can possibly be crashed by a user.  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=ftp://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>
Legend:
Removed from v.1.202  
changed lines
  Added in v.1.203