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