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

File: [local] / www / errata25.html (download) (as text)

Revision 1.69, Sat Jul 23 14:19:32 2016 UTC (7 years, 10 months ago) by deraadt
Branch: MAIN
Changes since 1.68: +3 -2 lines

rotate errata files to prepare for next release

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>OpenBSD 2.5 Errata</title>
<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">
<link rel="stylesheet" type="text/css" href="openbsd.css">
<link rel="canonical" href="http://www.openbsd.org/errata25.html">
</head>

<!--
			IMPORTANT REMINDER
	IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE
-->

<body bgcolor="#ffffff" text="#000000" link="#23238E">

<h2>
<a href="index.html">
<font color="#0000ff"><i>Open</i></font><font color="#000084">BSD</font></a>
<font color="#e00000">2.5 Errata</font>
</h2>
<hr>

<a href=stable.html>For OpenBSD patch branch information, please refer here.</a><br>
<br>
For errata on a certain release, click below:<br>
<a href="errata21.html">2.1</a>,
<a href="errata22.html">2.2</a>,
<a href="errata23.html">2.3</a>,
<a href="errata24.html">2.4</a>,
<a href="errata26.html">2.6</a>,
<a href="errata27.html">2.7</a>,
<a href="errata28.html">2.8</a>,
<a href="errata29.html">2.9</a>,
<a href="errata30.html">3.0</a>,
<a href="errata31.html">3.1</a>,
<a href="errata32.html">3.2</a>,
<a href="errata33.html">3.3</a>,
<a href="errata34.html">3.4</a>,
<a href="errata35.html">3.5</a>,
<a href="errata36.html">3.6</a>,
<a href="errata37.html">3.7</a>,
<br>
<a href="errata38.html">3.8</a>,
<a href="errata39.html">3.9</a>,
<a href="errata40.html">4.0</a>,
<a href="errata41.html">4.1</a>,
<a href="errata42.html">4.2</a>,
<a href="errata43.html">4.3</a>,
<a href="errata44.html">4.4</a>,
<a href="errata45.html">4.5</a>,
<a href="errata46.html">4.6</a>,
<a href="errata47.html">4.7</a>,
<a href="errata48.html">4.8</a>,
<a href="errata49.html">4.9</a>,
<a href="errata50.html">5.0</a>,
<a href="errata51.html">5.1</a>,
<a href="errata52.html">5.2</a>,
<a href="errata53.html">5.3</a>,
<br>
<a href="errata54.html">5.4</a>,
<a href="errata55.html">5.5</a>,
<a href="errata56.html">5.6</a>,
<a href="errata57.html">5.7</a>,
<a href="errata58.html">5.8</a>,
<a href="errata59.html">5.9</a>,
<a href="errata60.html">6.0</a>.
<br>
<hr>

<a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.5.tar.gz">
You can also fetch a tar.gz file containing all the following patches</a>.
This file is updated once a day.
<p>

The patches below are available in CVS via the
<code>OPENBSD_2_5</code> <a href="stable.html">patch branch</a>.
<p>

For more detailed information on how to install patches to OpenBSD, please
consult the <a href="./faq/faq10.html#Patches">OpenBSD FAQ</a>.
<p>

<hr>

<ul>
<li id="cron">
<font color="#009000"><strong>SECURITY FIX: Aug 30, 1999</strong></font>
&nbsp; <i>All architectures</i><br>
In cron(8), make sure argv[] is NULL terminated in the fake popen() and
run sendmail as the user, not as root.
<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>
<p>
<li id="miscfs">
<font color="#009000"><strong>SECURITY FIX: Aug 12, 1999</strong></font>
&nbsp; <i>All architectures</i><br>
The procfs and fdescfs filesystems had an overrun in their handling
of uio_offset in their readdir() routines. (These filesystems are not
enabled by default).
<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>
<p>
<li id="profil">
<font color="#009000"><strong>SECURITY FIX: Aug 9, 1999</strong></font>
&nbsp; <i>All architectures</i><br>
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 source code patch exists which remedies this problem.</a>
<p>
<li id="ipsec_in_use">
<font color="#009000"><strong>SECURITY FIX: Aug 6, 1999</strong></font>
&nbsp; <i>All architectures</i><br>
Packets that should have been handled by IPsec may be transmitted
as cleartext. PF_KEY SA expirations may leak kernel resources.
<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>
<p>
<li id="rc">
<font color="#009000"><strong>SECURITY FIX: Aug 5, 1999</strong></font>
&nbsp; <i>All architectures</i><br>
In /etc/rc, use mktemp(1) for motd re-writing, and change the find(1)
to use -execdir.
<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>
<p>
<li id="chflags">
<font color="#009000"><strong>SECURITY FIX: Jul 30, 1999</strong></font>
&nbsp; <i>All architectures</i><br>
Do not permit regular users to chflags(2) or fchflags(2) on character or
block devices which they may currently be the owner of.
<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>
<p>
<li id="nroff">
<font color="#009000"><strong>SECURITY FIX: Jul 27, 1999</strong></font>
&nbsp; <i>All architectures</i><br>
Cause groff(1) to be invoked with the -S flag, when called by nroff(1),
to avoid various groff features which may be security issues.  On the
whole, this is not really a security issue, but it was discussed on
BUGTRAQ as if it is.
<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>
<p>
<li id="fts">
<font color="#009000"><strong>RELIABILITY FIX: May 19, 1999</strong></font>
&nbsp; <i>All architectures</i><br>
Programs using fts(3) could dump core when given a directory structure
with a very large number of entries.
<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>
<p>
<li id="tcpsack">
<font color="#009000"><strong>RELIABILITY FIX: May 19, 1999</strong></font>
&nbsp; <i>All architectures</i><br>
Sequence numbers could wrap with TCP_SACK and TCP_NEWRENO, resulting in
failure to retransmit correctly.
<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>
<p>
<li id="ipsec1">
<font color="#009000"><strong>RELIABILITY FIX</strong></font>
&nbsp; <i>All architectures</i><br>
Retransmitted TCP packets could get corrupted when flowing over an
IPSEC ESP tunnel.
<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>
<p>
<li id="bmap">
<font color="#009000"><strong>RELIABILITY FIX</strong></font>
&nbsp; <i>All architectures</i><br>
A local user can crash the system by reading a file larger than 64meg
from an ext2fs partition.
<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>
<p>
<li id="pfkey">
<font color="#009000"><strong>RELIABILITY FIX</strong></font>
&nbsp; <i>All architectures</i><br>
PF_KEY socket operations leak internal kernel resources, so that a
system running an IPsec key management daemon like photurisd or isakmpd
will cause the networking subsystem to stop working after a finite amount
of time.
<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>
<p>
<li id="y2k">
<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
release (released at 1 Dec 1999) has this problem solved. This patch is
just a workaround.
<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>
<p>
<li id="brooktree">
<font color="#009000"><strong>RELIABILITY FIX</strong></font><br>
If a user opened the brooktree device on a system where it did not exist,
the kernel crashed.
<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>
<p>
<li id="macutils">
<font color="#009000"><strong>INSTALL PROBLEM</strong></font><br>
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
FTP install directories.  See
<a href="http://ftp.openbsd.org/pub/OpenBSD/2.5/mac68k/utils">
http://ftp.openbsd.org/pub/OpenBSD/2.5/mac68k/utils</a>
<p>
<li id="powerpc_trap">
<font color="#009000"><strong>RELIABILITY FIX</strong></font><br>
Two problems in the powerpc kernel trap handling cause severe system
unreliability.
<a href="http://ftp.openbsd.org/pub/OpenBSD/patches/2.5/powerpc/001_trap.patch">
A source code patch exists which remedies this problem.</a>
<p>

</ul>

<hr>

</body>
</html>