Annotation of www/errata.html, Revision 1.92
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.90 deraadt 24: <a name=rmjob></a>
25: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
26: An exploitable buffer mismanagement exists in a subroutine used by
1.92 ! deraadt 27: lprm and lpd. The problem is exploitable by users on a particular
! 28: machine if there is an entry in <strong>/etc/printcap</strong> which
! 29: points at a remote printer.
1.90 deraadt 30: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/rmjob.patch>
31: A patch is available which corrects this behaviour</a>.
32: <p>
1.89 deraadt 33: <a name=uucpd></a>
34: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
1.92 ! deraadt 35: A DNS-based vulnerability exists when uucpd is used. By default uucpd
! 36: is not enabled in the OpenBSD releases, but some sites may have enabled it.
1.89 deraadt 37: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/uucpd.patch>
38: A patch is available which corrects this behaviour</a>.
39: <p>
1.87 deraadt 40: <a name=named></a>
41: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
42: A vulnerability exists when (and only when) /etc/named.conf has the
1.88 deraadt 43: <strong>fake-iquery</strong> option enabled.
1.87 deraadt 44: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/named.patch>
45: A patch is available which corrects this behaviour</a>.
46: <p>
47: <a name=ping></a>
48: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
49: A vulnerability exists in ping(8); if the -R option is used to record
50: routes, an attacker can spoof a reply packet that will overflow inside
1.88 deraadt 51: ping. Preliminary investigation makes it look the worst attack
52: possible is to make ping crash, but one never knows...
1.87 deraadt 53: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/ping.patch>
54: A patch is available which corrects this behaviour</a>.
55: <p>
1.72 deraadt 56: <a name=sourceroute></a>
57: <li><strong><font color=#009000>SECURITY FIX</strong></font><br>
58: If the sysctl variable <strong>net.inet.ip.forwarding</strong> is
59: enabled (value 1), but the variable <strong>net.inet.ip.sourceroute</strong>
1.73 deraadt 60: is disabled (value 0), the kernel will block source routed packets from
61: going through, but will still accept source routing packets destined for
1.72 deraadt 62: itself. Our fix changes the <strong>net.inet.ip.sourceroute</strong>
1.77 deraadt 63: variable semantics to mean that all source routed packets should
1.73 deraadt 64: be blocked completely.
1.72 deraadt 65: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/sourceroute.patch>
66: A kernel patch is provided</a>.
1.39 deraadt 67: <p>
1.62 deraadt 68: <a name=ruserok></a>
1.72 deraadt 69: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
1.61 deraadt 70: A combination localhost+remote host security problem exists if a
71: local user running a setuid binary causes a non-existant root .rhosts
72: file to be created via a symbolic link with a specific kind of corefile,
73: and then subsequently uses rsh/rlogin to enter the machine from remote.
74: A similar exploit might also be possible using sshd which lacks any code
75: for checking for deviations from the expected format in the .rhosts or
76: .shosts files, but we have not confirmed this yet. The following two
77: fixes are recommended:
78: <p>
79: <ul>
80: <li>
81: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/nosuidcoredump.patch>
1.72 deraadt 82: (1) A kernel patch which adds a new sysctl option which permits the
83: administrator to decide whether setuid corefiles should be written or not</a>.
1.61 deraadt 84: <p>
85: <li><a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/rcmd.patch>
1.74 deraadt 86: (2) Replaces the libc ruserok() function with a more paranoid
87: version which detects bogus looking .rhosts files better.</a>
1.61 deraadt 88: </ul>
89: <p>
1.74 deraadt 90: If the
91: first patch is used to stop setuid coredumps, then the second patch is
92: not as important.
1.61 deraadt 93: This problem is fixed much better in OpenBSD-current, where the kernel's
94: symbolic link handling has been improved such that coredumping will not
95: create a file on the other side of a symbolic link. Such a patch is not
1.81 deraadt 96: possible for the 4.4lite1 VFS layer in the OpenBSD 2.2 kernel.<p>
97: The problem with the ruserok() function appears to also exist in
98: ssh 1.2.21 and previous (the ssh people have been alerted).
1.61 deraadt 99: <p>
1.72 deraadt 100: <a name=mmap></a>
101: <li><strong><font color=#009000>SECURITY FIX</strong></font><br>
1.80 deraadt 102: A bug in the vm system permits a file descriptor opened read-only on a
103: device, to later on be mmap(2)'d read-write, and then modified. This
104: does not result in a security hole by itself, but it does violate the
105: safety semantics which securelevels are supposed to provide. If a user
106: manages to gain kmem group permissions, using this problem they can then
107: gain root trivially and/or turn securelevels off.
1.72 deraadt 108: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/vm_mmap.patch>
1.79 deraadt 109: A kernel patch is available which corrects this behaviour (this is
1.83 deraadt 110: revision 3 of this patch)</a>.
1.72 deraadt 111: <p>
112: <li><font color=#009000><strong>BUILD PROCESS FIX</strong></font><br>
113: Building an object tree from a read-only source tree (such as off a CDROM)
114: may fail under certain circumstances (e.g. when creating a symlink on sparc
115: whose target name is exactly 33 characters). As a workaround you have to
116: either provide the source tree read/write, or install a newer version of
117: /usr/bin/readlink.
118: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/readlink.c>
119: A replacement source file exists</a>.
120: <p>
1.85 deraadt 121: <a name=mountd></a>
1.84 deraadt 122: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
123: If a line in /etc/exports which contains hostnames results in an empty
124: list because none of the supplied hostnames is known, mountd(8) will
125: accidentally export the filesystem to the world.
126: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/mountd.patch>
127: A patch is available which corrects this behaviour</a>.
128: <p>
1.86 millert 129: <li><font color=#009000><strong>RELIABILITY FIX</strong></font><br>
130: Setting the MSG_EOR flag on a tcp packet in the send(2) family of
131: system calls could cause a kernel panic.
132: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/send.patch>
133: A patch</a> to return EINVAL in this case is available.
134: <p>
1.25 deraadt 135: </ul>
1.42 deraadt 136: <a name=i386></a>
1.67 deraadt 137: <li><h3><font color=#e00000>i386</font></h3>
1.25 deraadt 138: <ul>
1.76 deraadt 139: <a name=f00f></a>
1.72 deraadt 140: <li><font color=#009000><strong>RELIABILITY FIX</strong></font><br>
141: The Intel P5 F00F bug was discovered after the CDR's had already been
1.39 deraadt 142: sent to the manufacturer. This problem permits any user who has an account
143: to lock your machine up using a 4-line program. The problem only affects
144: Intel P5 processors (the i386, i486, P-Pro, and P-II are not vulnerable,
145: nor are processors by other manufacturers).
1.44 deraadt 146: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/i386/f00f.patch>
1.39 deraadt 147: A kernel source-code patch is available</a>.
148: <p>
1.72 deraadt 149: <li><font color=#009000><strong>FUNCTIONALITY FIX</strong></font><br>
150: Some Linux binaries will execute in SVR4 emulation mode, which is
1.33 deraadt 151: definately a problem for people who need Linux emulation to work correctly.
1.39 deraadt 152: To solve this mis-identification problem,
1.32 deraadt 153: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/i386/compat_linux.patch>
1.72 deraadt 154: a patch file is provided</a>.
1.39 deraadt 155: <p>
1.72 deraadt 156: <li><font color=#009000><strong>RELIABILITY FIX</strong></font><br>
157: APM can crash on machines without it.
1.45 deraadt 158: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/i386/apm.patch>
159: A kernel source-code patch is available</a>.
160: <p>
1.72 deraadt 161: <li><font color=#009000><strong>INSTALLATION PROCESS FLAW</strong></font><br>
162: A few people are running into this problem, particularily if they had some
1.39 deraadt 163: other *BSD operating system on their machine before trying OpenBSD: if after
164: installation onto an IDE-based machine, the kernel fails to mount the root
165: partition because it thinks that it should be opening sd0 (0x400), this means
166: you have incorrectly setup your disklabel for the IDE drive -- the disklabel
167: is indicating that the drive is SCSI.
168: To repair this, use the floppy to run "disklabel -E wd0", then using the
169: "edit" command ensure the type field is set to "ST506".
170: <p>
171: </ul>
1.47 deraadt 172: <a name=mac68k></a>
1.67 deraadt 173: <li><h3><font color=#e00000>mac68k</font></h3>
1.39 deraadt 174: <ul>
1.72 deraadt 175: <li><font color=#009000><strong>NEW SOFTWARE</strong></font><br>
176: Unfortunately, X11 binaries for the mac68k did not manage to make it onto the
1.69 deraadt 177: CDROM. However, X11 for the mac68k is immediately available from
1.46 gene 178: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/2.2/mac68k/X11/X11R6.tar.gz">
179: ftp://ftp.OpenBSD.org/pub/OpenBSD/2.2/mac68k/X11/X11R6.tar.gz</a>. Please
180: 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
181: and setting up X.
1.39 deraadt 182: <p>
1.72 deraadt 183: <li><font color=#009000><strong>INSTALLATION PROCESS FLAW</strong></font><br>
184: As shipped on the CDROM, both the
185: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/2.2/mac68k/bsd-generic.tar.gz">
186: generic kernel</a>
187: and the
1.70 gene 188: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/2.2/bsd-genericbsc.tar.gz">
1.72 deraadt 189: genericsbc kernel</a>
190: extract themselves into the wrong place in the filesystem.
1.70 gene 191: Both <strong>should</strong> extract a kernel named <tt>/bsd</tt>, but they extract
192: the kernel into <tt>/usr/src/sys/arch/mac68k/compile</tt> instead.
193: <p>
1.74 deraadt 194: This has been fixed on the ftp release of <a href=22.html>OpenBSD 2.2</a>, and
1.71 gene 195: fresh kernels are available from <a href="ftp://ftp.openbsd.org/pub/OpenBSD/2.2/mac68k">
196: ftp://ftp.OpenBSD.ORG/pub/OpenBSD/2.2/mac68k/</a>. If at all possible,
197: installing these kernels is recommended.
198: <p>
199: A number of possible workarounds exist if you don't have easy access to ftp
200: the updated kernels. The simplest of these is to use a
1.70 gene 201: MacOS program to uncompress and untar the kernel aad use the Installer's
202: mini-shell to "cpin" the kernel. Alternately, you could install the kernel
203: with the Installer and use the mini-shell to move the binary from <tt>/usr/src/...</tt> to <tt>/bsd</tt>.
204: <p>
1.25 deraadt 205: </ul>
1.65 deraadt 206: <a name=sparc></a>
1.67 deraadt 207: <li><h3><font color=#e00000>sparc</font></h3>
1.25 deraadt 208: <ul>
1.72 deraadt 209: <li><font color=#009000><strong>RELIABILITY FIX</strong></font><br>
210: Older 4/xxx systems (particularily the 4/300's) cannot boot
1.58 deraadt 211: with the 2.2 kernel due to bugs in the scsi device driver.
1.57 jason 212: <a href=ftp://ftp.OpenBSD.org/pub/OpenBSD/patches/2.2/sparc/esp.patch>
1.72 deraadt 213: A kernel source patch is available</a>.
1.60 jason 214: Replacement kernels are available for:
215: <a href=ftp://ftp.OpenBSD.org/pub/OpenBSD/patches/2.2/sparc/bsd>bsd</a>,
216: <a href=ftp://ftp.OpenBSD.org/pub/OpenBSD/patches/2.2/sparc/bsd.scsi3>bsd.scsi3</a>,
217: and a replacement for bsd.rd is coming soon.
1.39 deraadt 218: <p>
1.65 deraadt 219: <a name=sparciommu></a>
1.72 deraadt 220: <li><font color=#009000><strong>RELIABILITY FIX</strong></font><br>
221: SPARCstation 4 and 5 (Microsparc 2) users may see kernel panics when
1.63 marc 222: using a custom kernel configured for option sun4m only.
223: <a href=ftp://ftp.OpenBSD.org/pub/OpenBSD/patches/2.2/sparc/sun4m.patch>
1.72 deraadt 224: A workaround (kernel source patch) is available</a>. Apply the patch and
1.63 marc 225: then re-build your kernel.
226: <p>
1.39 deraadt 227: </ul>
1.67 deraadt 228: <li><h3><font color=#e00000>amiga</font></h3>
1.39 deraadt 229: <p>
230: <ul>
1.72 deraadt 231: <li><font color=#009000><strong>FUNCTIONALITY FIX</strong></font><br>
232: Missing Xamiga manual pages. Get
1.48 niklas 233: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/amiga/Xamiga-manual.tgz>
234: this package</a> and execute, <i>as root</i>:<br>
1.74 deraadt 235: <strong><b># </b>pkg_add Xamiga-manual.tgz</strong><br>
1.51 deraadt 236: The MD5 checksum of this package is:<br>
1.49 deraadt 237: <b>MD5 (Xamiga-manual.tgz) = 2362a7857264b9d17f65cca258b42031</b><p>
1.72 deraadt 238: <li><font color=#009000><strong>FUNCTIONALITY FIX</strong></font><br>
239: The Ariadne ethernet support was broken, there will be both binary and
1.48 niklas 240: source level fixes available shortly. If you are in a hurry mail
1.49 deraadt 241: <a href=mailto:niklas@openbsd.org>Niklas</a> for a test kernel.<p>
1.25 deraadt 242: </ul>
1.65 deraadt 243: <a name=pmax></a>
1.67 deraadt 244: <li><h3><font color=#e00000>pmax</font></h3>
1.25 deraadt 245: <ul>
1.72 deraadt 246: <li><font color=#009000><strong>FUNCTIONALITY FIX</strong></font><br>
247: There is a Year-1998 problem in the time-setting code (which causes the
1.53 deraadt 248: date and time to be set incorrectly after a reboot in 1998).
249: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/clock.patch>
1.72 deraadt 250: A source code patch file is available</a> plus replacement installation
1.53 deraadt 251: kernels for the 2.2 release at
252: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/bsd.NFS>bsd.NFS</a>,
253: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/bsd>bsd</a>,
254: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/bsd.rz0>bsd.rz0</a>.
1.66 deraadt 255: <p>
1.72 deraadt 256: <li><font color=#009000><strong>FUNCTIONALITY FIX</strong></font><br>
257: X11 support for the 3min and 3maxplus machines was broken
1.53 deraadt 258: due to a kernel bug.
259: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/fb.patch>
260: A source code patch is available</a>.
1.66 deraadt 261: <p>
1.82 deraadt 262: <a name=ldso></a>
1.72 deraadt 263: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
1.82 deraadt 264: A security problem in the shared library linker <strong>ld.so</strong>
265: requires that you replace it with a new binary. The following binary
266: will work on both pmax and arc machines.
267: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/ld.so>
1.72 deraadt 268: The replacement binary is here</a>.
1.39 deraadt 269: <p>
1.25 deraadt 270: </ul>
1.65 deraadt 271: <a name=arc></a>
1.67 deraadt 272: <li><h3><font color=#e00000>arc</font></h3>
1.59 deraadt 273: <ul>
1.72 deraadt 274: <li><font color=#009000><strong>SECURITY FIX</strong></font><br>
275: A security problem in the shared library linker <strong>ld.so</strong> requires
1.82 deraadt 276: that you replace it with a new binary. The following binary
277: will work on both pmax and arc machines.
278: <a href=ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/ld.so>
1.72 deraadt 279: The replacement binary is here</a>.
1.69 deraadt 280: <p>
1.59 deraadt 281: </ul>
1.67 deraadt 282: <li><h3><font color=#e00000>alpha</font></h3>
1.56 deraadt 283: <p>
284: <ul>
1.82 deraadt 285: <li><font color=#009000><strong>MISSING FUNCTIONALITY</strong></font><br>
286: Network Address Translation and other parts of IP Filtering to not work
287: on the alpha. This will be fixed in the 2.3 release, and perhaps earlier
288: in a snapshot. There is no patch for 2.2.
1.56 deraadt 289: <p>
290: </ul>
1.67 deraadt 291: <li><h3><font color=#e00000>hp300</font></h3>
1.56 deraadt 292: <p>
293: <ul>
294: <li>No problems identified yet.
295: <p>
296: </ul>
1.67 deraadt 297: <li><h3><font color=#e00000>mvme68k</font></h3>
1.25 deraadt 298: <ul>
1.39 deraadt 299: <li>No problems identified yet.
300: <p>
1.25 deraadt 301: </ul>
302: </ul>
303: <br>
1.75 deraadt 304:
1.25 deraadt 305: <hr>
1.75 deraadt 306: <a href=errata21.html>For 2.1 errata, please refer here</a>.
1.2 deraadt 307: <hr>
308: <a href=orders.html><img src=back.gif border=0 alt=OpenBSD></a>
309: <a href=mailto:www@openbsd.org>www@openbsd.org</a>
1.92 ! deraadt 310: <br><small>$OpenBSD: errata.html,v 1.91 1998/04/22 14:52:49 deraadt Exp $</small>
1.2 deraadt 311:
312: </body>
313: </html>