Annotation of www/errata.html, Revision 1.76
1.1 deraadt 1: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML Strict//EN">
2: <html>
3: <head>
1.64 deraadt 4: <title>OpenBSD release errata</title>
1.1 deraadt 5: <link rev=made href=mailto:www@openbsd.org>
6: <meta name="resource-type" content="document">
7: <meta name="description" content="the OpenBSD CD errata page">
8: <meta name="keywords" content="openbsd,cd,errata">
9: <meta name="distribution" content="global">
10: <meta name="copyright" content="This document copyright 1997 by OpenBSD.">
11: </head>
12:
13: <BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#23238E">
14:
1.37 deraadt 15: <img alt="[OpenBSD]" SRC="images/smalltitle.gif">
1.68 deraadt 16: <h2><font color=#0000e0>
17: This is the OpenBSD 2.2 release errata & patch list:
18: </font></h2>
19:
1.25 deraadt 20: <ul>
1.43 deraadt 21: <a name=all></a>
1.67 deraadt 22: <li><h3><font color=#e00000>All architectures</font></h3>
1.25 deraadt 23: <ul>
1.72 deraadt 24: <a name=sourceroute></a>
25: <li><strong><font color=#009000>SECURITY FIX</strong></font><br>
26: If the sysctl variable <strong>net.inet.ip.forwarding</strong> is
27: enabled (value 1), but the variable <strong>net.inet.ip.sourceroute</strong>
1.73 deraadt 28: is disabled (value 0), the kernel will block source routed packets from
29: going through, but will still accept source routing packets destined for
1.72 deraadt 30: itself. Our fix changes the <strong>net.inet.ip.sourceroute</strong>
1.73 deraadt 31: variable semantics to mean that all block all source routed packets should
32: be blocked completely.
1.72 deraadt 33: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/sourceroute.patch>
34: A kernel patch is provided</a>.
1.39 deraadt 35: <p>
1.62 deraadt 36: <a name=ruserok></a>
1.72 deraadt 37: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
1.61 deraadt 38: A combination localhost+remote host security problem exists if a
39: local user running a setuid binary causes a non-existant root .rhosts
40: file to be created via a symbolic link with a specific kind of corefile,
41: and then subsequently uses rsh/rlogin to enter the machine from remote.
42: A similar exploit might also be possible using sshd which lacks any code
43: for checking for deviations from the expected format in the .rhosts or
44: .shosts files, but we have not confirmed this yet. The following two
45: fixes are recommended:
46: <p>
47: <ul>
48: <li>
49: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/nosuidcoredump.patch>
1.72 deraadt 50: (1) A kernel patch which adds a new sysctl option which permits the
51: administrator to decide whether setuid corefiles should be written or not</a>.
1.61 deraadt 52: <p>
53: <li><a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/rcmd.patch>
1.74 deraadt 54: (2) Replaces the libc ruserok() function with a more paranoid
55: version which detects bogus looking .rhosts files better.</a>
1.61 deraadt 56: </ul>
57: <p>
1.74 deraadt 58: If the
59: first patch is used to stop setuid coredumps, then the second patch is
60: not as important.
1.61 deraadt 61: This problem is fixed much better in OpenBSD-current, where the kernel's
62: symbolic link handling has been improved such that coredumping will not
63: create a file on the other side of a symbolic link. Such a patch is not
64: possible for the 4.4lite1 VFS layer in the OpenBSD 2.2 kernel.
65: <p>
1.72 deraadt 66: <a name=mmap></a>
67: <li><strong><font color=#009000>SECURITY FIX</strong></font><br>
68: If you rely on the system securelevels as described in init(8), you
69: will want this fix. A bug in the vm system permits a file descriptor
70: opened read-only on a device, to later on be mmap(2)'d read-write, and
71: then modified. This does not result in a security hole by itself, but
72: it does violate the safety semantics which securelevels are supposed to
73: provide.
74: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/vm_mmap.patch>
75: A kernel patch is available which corrects this behaviour</a>.
76: <p>
77: <li><font color=#009000><strong>BUILD PROCESS FIX</strong></font><br>
78: Building an object tree from a read-only source tree (such as off a CDROM)
79: may fail under certain circumstances (e.g. when creating a symlink on sparc
80: whose target name is exactly 33 characters). As a workaround you have to
81: either provide the source tree read/write, or install a newer version of
82: /usr/bin/readlink.
83: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/readlink.c>
84: A replacement source file exists</a>.
85: <p>
1.25 deraadt 86: </ul>
1.42 deraadt 87: <a name=i386></a>
1.67 deraadt 88: <li><h3><font color=#e00000>i386</font></h3>
1.25 deraadt 89: <ul>
1.76 ! deraadt 90: <a name=f00f></a>
1.72 deraadt 91: <li><font color=#009000><strong>RELIABILITY FIX</strong></font><br>
92: The Intel P5 F00F bug was discovered after the CDR's had already been
1.39 deraadt 93: sent to the manufacturer. This problem permits any user who has an account
94: to lock your machine up using a 4-line program. The problem only affects
95: Intel P5 processors (the i386, i486, P-Pro, and P-II are not vulnerable,
96: nor are processors by other manufacturers).
1.44 deraadt 97: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/i386/f00f.patch>
1.39 deraadt 98: A kernel source-code patch is available</a>.
99: <p>
1.72 deraadt 100: <li><font color=#009000><strong>FUNCTIONALITY FIX</strong></font><br>
101: Some Linux binaries will execute in SVR4 emulation mode, which is
1.33 deraadt 102: definately a problem for people who need Linux emulation to work correctly.
1.39 deraadt 103: To solve this mis-identification problem,
1.32 deraadt 104: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/i386/compat_linux.patch>
1.72 deraadt 105: a patch file is provided</a>.
1.39 deraadt 106: <p>
1.72 deraadt 107: <li><font color=#009000><strong>RELIABILITY FIX</strong></font><br>
108: APM can crash on machines without it.
1.45 deraadt 109: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/i386/apm.patch>
110: A kernel source-code patch is available</a>.
111: <p>
1.72 deraadt 112: <li><font color=#009000><strong>INSTALLATION PROCESS FLAW</strong></font><br>
113: A few people are running into this problem, particularily if they had some
1.39 deraadt 114: other *BSD operating system on their machine before trying OpenBSD: if after
115: installation onto an IDE-based machine, the kernel fails to mount the root
116: partition because it thinks that it should be opening sd0 (0x400), this means
117: you have incorrectly setup your disklabel for the IDE drive -- the disklabel
118: is indicating that the drive is SCSI.
119: To repair this, use the floppy to run "disklabel -E wd0", then using the
120: "edit" command ensure the type field is set to "ST506".
121: <p>
122: </ul>
1.47 deraadt 123: <a name=mac68k></a>
1.67 deraadt 124: <li><h3><font color=#e00000>mac68k</font></h3>
1.39 deraadt 125: <ul>
1.72 deraadt 126: <li><font color=#009000><strong>NEW SOFTWARE</strong></font><br>
127: Unfortunately, X11 binaries for the mac68k did not manage to make it onto the
1.69 deraadt 128: CDROM. However, X11 for the mac68k is immediately available from
1.46 gene 129: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/2.2/mac68k/X11/X11R6.tar.gz">
130: ftp://ftp.OpenBSD.org/pub/OpenBSD/2.2/mac68k/X11/X11R6.tar.gz</a>. Please
131: 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
132: and setting up X.
1.39 deraadt 133: <p>
1.72 deraadt 134: <li><font color=#009000><strong>INSTALLATION PROCESS FLAW</strong></font><br>
135: As shipped on the CDROM, both the
136: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/2.2/mac68k/bsd-generic.tar.gz">
137: generic kernel</a>
138: and the
1.70 gene 139: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/2.2/bsd-genericbsc.tar.gz">
1.72 deraadt 140: genericsbc kernel</a>
141: extract themselves into the wrong place in the filesystem.
1.70 gene 142: Both <strong>should</strong> extract a kernel named <tt>/bsd</tt>, but they extract
143: the kernel into <tt>/usr/src/sys/arch/mac68k/compile</tt> instead.
144: <p>
1.74 deraadt 145: This has been fixed on the ftp release of <a href=22.html>OpenBSD 2.2</a>, and
1.71 gene 146: fresh kernels are available from <a href="ftp://ftp.openbsd.org/pub/OpenBSD/2.2/mac68k">
147: ftp://ftp.OpenBSD.ORG/pub/OpenBSD/2.2/mac68k/</a>. If at all possible,
148: installing these kernels is recommended.
149: <p>
150: A number of possible workarounds exist if you don't have easy access to ftp
151: the updated kernels. The simplest of these is to use a
1.70 gene 152: MacOS program to uncompress and untar the kernel aad use the Installer's
153: mini-shell to "cpin" the kernel. Alternately, you could install the kernel
154: with the Installer and use the mini-shell to move the binary from <tt>/usr/src/...</tt> to <tt>/bsd</tt>.
155: <p>
1.25 deraadt 156: </ul>
1.65 deraadt 157: <a name=sparc></a>
1.67 deraadt 158: <li><h3><font color=#e00000>sparc</font></h3>
1.25 deraadt 159: <ul>
1.72 deraadt 160: <li><font color=#009000><strong>RELIABILITY FIX</strong></font><br>
161: Older 4/xxx systems (particularily the 4/300's) cannot boot
1.58 deraadt 162: with the 2.2 kernel due to bugs in the scsi device driver.
1.57 jason 163: <a href=ftp://ftp.OpenBSD.org/pub/OpenBSD/patches/2.2/sparc/esp.patch>
1.72 deraadt 164: A kernel source patch is available</a>.
1.60 jason 165: Replacement kernels are available for:
166: <a href=ftp://ftp.OpenBSD.org/pub/OpenBSD/patches/2.2/sparc/bsd>bsd</a>,
167: <a href=ftp://ftp.OpenBSD.org/pub/OpenBSD/patches/2.2/sparc/bsd.scsi3>bsd.scsi3</a>,
168: and a replacement for bsd.rd is coming soon.
1.39 deraadt 169: <p>
1.65 deraadt 170: <a name=sparciommu></a>
1.72 deraadt 171: <li><font color=#009000><strong>RELIABILITY FIX</strong></font><br>
172: SPARCstation 4 and 5 (Microsparc 2) users may see kernel panics when
1.63 marc 173: using a custom kernel configured for option sun4m only.
174: <a href=ftp://ftp.OpenBSD.org/pub/OpenBSD/patches/2.2/sparc/sun4m.patch>
1.72 deraadt 175: A workaround (kernel source patch) is available</a>. Apply the patch and
1.63 marc 176: then re-build your kernel.
177: <p>
1.39 deraadt 178: </ul>
1.67 deraadt 179: <li><h3><font color=#e00000>amiga</font></h3>
1.39 deraadt 180: <p>
181: <ul>
1.72 deraadt 182: <li><font color=#009000><strong>FUNCTIONALITY FIX</strong></font><br>
183: Missing Xamiga manual pages. Get
1.48 niklas 184: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/amiga/Xamiga-manual.tgz>
185: this package</a> and execute, <i>as root</i>:<br>
1.74 deraadt 186: <strong><b># </b>pkg_add Xamiga-manual.tgz</strong><br>
1.51 deraadt 187: The MD5 checksum of this package is:<br>
1.49 deraadt 188: <b>MD5 (Xamiga-manual.tgz) = 2362a7857264b9d17f65cca258b42031</b><p>
1.72 deraadt 189: <li><font color=#009000><strong>FUNCTIONALITY FIX</strong></font><br>
190: The Ariadne ethernet support was broken, there will be both binary and
1.48 niklas 191: source level fixes available shortly. If you are in a hurry mail
1.49 deraadt 192: <a href=mailto:niklas@openbsd.org>Niklas</a> for a test kernel.<p>
1.25 deraadt 193: </ul>
1.65 deraadt 194: <a name=pmax></a>
1.67 deraadt 195: <li><h3><font color=#e00000>pmax</font></h3>
1.25 deraadt 196: <ul>
1.72 deraadt 197: <li><font color=#009000><strong>FUNCTIONALITY FIX</strong></font><br>
198: There is a Year-1998 problem in the time-setting code (which causes the
1.53 deraadt 199: date and time to be set incorrectly after a reboot in 1998).
200: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/clock.patch>
1.72 deraadt 201: A source code patch file is available</a> plus replacement installation
1.53 deraadt 202: kernels for the 2.2 release at
203: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/bsd.NFS>bsd.NFS</a>,
204: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/bsd>bsd</a>,
205: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/bsd.rz0>bsd.rz0</a>.
1.66 deraadt 206: <p>
1.72 deraadt 207: <li><font color=#009000><strong>FUNCTIONALITY FIX</strong></font><br>
208: X11 support for the 3min and 3maxplus machines was broken
1.53 deraadt 209: due to a kernel bug.
210: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/fb.patch>
211: A source code patch is available</a>.
1.66 deraadt 212: <p>
1.72 deraadt 213: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
214: A security problem in the shared library linker <strong>ld.so</strong> requires that
1.59 deraadt 215: you replace it with a new binary.
216: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2//pmax/ld.so>
1.72 deraadt 217: The replacement binary is here</a>.
1.39 deraadt 218: <p>
1.25 deraadt 219: </ul>
1.65 deraadt 220: <a name=arc></a>
1.67 deraadt 221: <li><h3><font color=#e00000>arc</font></h3>
1.59 deraadt 222: <ul>
1.72 deraadt 223: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
224: A security problem in the shared library linker <strong>ld.so</strong> requires
225: that you replace it with a new binary.
1.59 deraadt 226: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2//pmax/ld.so>
1.72 deraadt 227: The replacement binary is here</a>.
1.69 deraadt 228: <p>
1.59 deraadt 229: </ul>
1.67 deraadt 230: <li><h3><font color=#e00000>alpha</font></h3>
1.56 deraadt 231: <p>
232: <ul>
233: <li>No problems identified yet.
234: <p>
235: </ul>
1.67 deraadt 236: <li><h3><font color=#e00000>hp300</font></h3>
1.56 deraadt 237: <p>
238: <ul>
239: <li>No problems identified yet.
240: <p>
241: </ul>
1.67 deraadt 242: <li><h3><font color=#e00000>mvme68k</font></h3>
1.25 deraadt 243: <ul>
1.39 deraadt 244: <li>No problems identified yet.
245: <p>
1.25 deraadt 246: </ul>
247: </ul>
248: <br>
1.75 deraadt 249:
1.25 deraadt 250: <hr>
1.75 deraadt 251: <a href=errata21.html>For 2.1 errata, please refer here</a>.
1.2 deraadt 252: <hr>
253: <a href=orders.html><img src=back.gif border=0 alt=OpenBSD></a>
254: <a href=mailto:www@openbsd.org>www@openbsd.org</a>
1.76 ! deraadt 255: <br><small>$OpenBSD: errata.html,v 1.75 1998/02/19 11:28:00 deraadt Exp $</small>
1.2 deraadt 256:
257: </body>
258: </html>