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