www/errata.html - diff

Return to errata.html CVS log

Up to [local] / www

Diff for /www/errata.html between version 1.71 and 1.72

version 1.71, 1998/02/16 00:59:46

version 1.72, 1998/02/19 10:42:30

Line 21

<li><h3>All architectures</h3>

<ul>

<li>Building an object tree from a read-only source tree (such as off a CDROM)

may fail under certain circumstances (e.g. when creating a symlink on sparc

<li>SECURITY FIX

whose target name is exactly 33 characters). As a workaround you have to

If the sysctl variable net.inet.ip.forwarding is

either provide the source tree read/write, or install a newer version of

enabled (value 1), but the variable net.inet.ip.sourceroute

/usr/bin/readlink. You wish to use

is disabled (value 0), the kernel will still accept source routing packets

itself. Our fix changes the net.inet.ip.sourceroute

revision 1.13 of usr.bin/readlink/readlink.c</a>.

variable to mean that all block all source routed packets should be

blocked completely.

A kernel patch is provided</a>.

<li>IMPORTANT

<li>SECURITY FIX

A combination localhost+remote host security problem exists if a

local user running a setuid binary causes a non-existant root .rhosts

file to be created via a symbolic link with a specific kind of corefile,

Line 43

Line 46

<ul>

<li>

(1) Adds a new sysctl option which permits the adminstrator to decide

(1) A kernel patch which adds a new sysctl option which permits the

whether setuid corefiles should be written or not.</a>

administrator to decide whether setuid corefiles should be written or not</a>.

(2) Replaces the ruserok() function in libc with a much more paranoid

version which can detect these bogus looking .rhosts files better. If the

previous patch is used to stop setuid coredumps, then this patch is not

as important.</a>

as important</a>.

</ul>

This problem is fixed much better in OpenBSD-current, where the kernel's

Line 58

Line 61

create a file on the other side of a symbolic link. Such a patch is not

possible for the 4.4lite1 VFS layer in the OpenBSD 2.2 kernel.

<li>SECURITY FIX

If you rely on the system securelevels as described in init(8), you

will want this fix. A bug in the vm system permits a file descriptor

opened read-only on a device, to later on be mmap(2)'d read-write, and

then modified. This does not result in a security hole by itself, but

it does violate the safety semantics which securelevels are supposed to

provide.

A kernel patch is available which corrects this behaviour</a>.

<li>BUILD PROCESS FIX

Building an object tree from a read-only source tree (such as off a CDROM)

may fail under certain circumstances (e.g. when creating a symlink on sparc

whose target name is exactly 33 characters). As a workaround you have to

either provide the source tree read/write, or install a newer version of

/usr/bin/readlink.

A replacement source file exists</a>.

</ul>

<ul>

<li>The Intel P5 F00F bug was discovered after the CDR's had already been

<li>RELIABILITY FIX

The Intel P5 F00F bug was discovered after the CDR's had already been

sent to the manufacturer. This problem permits any user who has an account

to lock your machine up using a 4-line program. The problem only affects

Intel P5 processors (the i386, i486, P-Pro, and P-II are not vulnerable,

Line 70

Line 94

A kernel source-code patch is available</a>.

<li>Some Linux binaries will execute in SVR4 emulation mode, which is

<li>FUNCTIONALITY FIX

Some Linux binaries will execute in SVR4 emulation mode, which is

definately a problem for people who need Linux emulation to work correctly.

To solve this mis-identification problem,

a patch file is provided.</a>

a patch file is provided</a>.

<li>APM can crash on machines without it.

<li>RELIABILITY FIX

APM can crash on machines without it.

A kernel source-code patch is available</a>.

<li>A few people are running into this problem, particularily if they had some

<li>INSTALLATION PROCESS FLAW

A few people are running into this problem, particularily if they had some

other *BSD operating system on their machine before trying OpenBSD: if after

installation onto an IDE-based machine, the kernel fails to mount the root

partition because it thinks that it should be opening sd0 (0x400), this means

Line 93

Line 120

<ul>

<li>Unfortunately, X11 binaries for the mac68k did not manage to make it onto the

<li>NEW SOFTWARE

Unfortunately, X11 binaries for the mac68k did not manage to make it onto the

CDROM. However, X11 for the mac68k is immediately available from

ftp://ftp.OpenBSD.org/pub/OpenBSD/2.2/mac68k/X11/X11R6.tar.gz</a>. Please

be sure to read the <a href="ftp://ftp.openbsd.org/pub/OpenBSD/2.2/mac68k/X11/README.X11">README file</a> also in that directory for instructions on installing

and setting up X.

<li>As shipped on the CDROM, both the <a href="ftp://ftp.openbsd.org/pub/OpenBSD/2.2/mac68k/bsd-generic.tar.gz">generic kernel</a> and the

<li>INSTALLATION PROCESS FLAW

As shipped on the CDROM, both the

generic kernel</a>

and the

genericsbc kernel</a> extract themselves into the wrong place in the filesystem.

genericsbc kernel</a>

extract themselves into the wrong place in the filesystem.

Both should extract a kernel named <tt>/bsd</tt>, but they extract

the kernel into <tt>/usr/src/sys/arch/mac68k/compile</tt> instead.

Line 121

Line 154

<li><h3>sparc</h3>

<ul>

<li>Older 4/xxx systems (particularily the 4/300's) cannot boot

<li>RELIABILITY FIX

Older 4/xxx systems (particularily the 4/300's) cannot boot

with the 2.2 kernel due to bugs in the scsi device driver.

A kernel source patch is available.</a>

A kernel source patch is available</a>.

Replacement kernels are available for:

<a href=ftp://ftp.OpenBSD.org/pub/OpenBSD/patches/2.2/sparc/bsd>bsd</a>,

<a href=ftp://ftp.OpenBSD.org/pub/OpenBSD/patches/2.2/sparc/bsd.scsi3>bsd.scsi3</a>,

and a replacement for bsd.rd is coming soon.

<li>SPARCstation 4 and 5 (Microsparc 2) users may see kernel panics when

<li>RELIABILITY FIX

SPARCstation 4 and 5 (Microsparc 2) users may see kernel panics when

using a custom kernel configured for option sun4m only.

A workaround (kernel source patch) is available.</a> Apply the patch and

A workaround (kernel source patch) is available</a>. Apply the patch and

then re-build your kernel.

</ul>

<li><h3>amiga</h3>

<ul>

<li>Missing Xamiga manual page. Get

<li>FUNCTIONALITY FIX

Missing Xamiga manual pages. Get

this package</a> and execute, as root:

<pre># pkg_add Xamiga-manual.tgz</pre>

The MD5 checksum of this package is:

MD5 (Xamiga-manual.tgz) = 2362a7857264b9d17f65cca258b42031

<li>The Ariadne ethernet support was broken, there will be both binary and

<li>FUNCTIONALITY FIX

The Ariadne ethernet support was broken, there will be both binary and

source level fixes available shortly. If you are in a hurry mail

<a href=mailto:niklas@openbsd.org>Niklas</a> for a test kernel.

</ul>

<ul>

<li>There is a Year-1998 problem in the time-setting code (which causes the

<li>FUNCTIONALITY FIX

There is a Year-1998 problem in the time-setting code (which causes the

date and time to be set incorrectly after a reboot in 1998).

A source code patch file is available.</a> plus replacement installation

A source code patch file is available</a> plus replacement installation

kernels for the 2.2 release at

<a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/bsd.NFS>bsd.NFS</a>,

<a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/bsd>bsd</a>,

<a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/bsd.rz0>bsd.rz0</a>.

<li>X11 support for the 3min and 3maxplus machines was broken

<li>FUNCTIONALITY FIX

X11 support for the 3min and 3maxplus machines was broken

due to a kernel bug.

A source code patch is available</a>.

<li>A bug in the shared library linker ld.so requires that

<li>SECURITY FIX

A security problem in the shared library linker ld.so requires that

you replace it with a new binary.

The replacement binary is here.</a>

The replacement binary is here</a>.

</ul>

<ul>

<li>A bug in the shared library linker ld.so requires that

<li>SECURITY FIX

you replace it with a new binary.

A security problem in the shared library linker ld.so requires

that you replace it with a new binary.

The replacement binary is here.</a>

The replacement binary is here</a>.

</ul>

<li><h3>alpha</h3>