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