Annotation of www/errata22.html, Revision 1.47
1.37 naddy 1: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
1.1 deraadt 2: <html>
3: <head>
1.19 deraadt 4: <title>OpenBSD 2.2 errata</title>
1.37 naddy 5: <link rev=made href="mailto:www@openbsd.org">
1.1 deraadt 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">
1.27 jufi 10: <meta name="copyright" content="This document copyright 1997-2001 by OpenBSD.">
1.41 henning 11: <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
1.1 deraadt 12: </head>
13:
1.42 david 14: <body bgcolor="#ffffff" text="#000000" link="#23238E">
1.1 deraadt 15:
1.32 jsyn 16: <a href="index.html"><img alt="[OpenBSD]" height="30" width="141" src="images/smalltitle.gif" border="0"></a>
1.37 naddy 17: <h2><font color="#0000e0">
1.14 espie 18: This is the OpenBSD 2.2 release errata & patch list:
1.1 deraadt 19: </font></h2>
20:
1.2 deraadt 21: <hr>
1.20 jason 22: <a href=stable.html>For OpenBSD patch branch information, please refer here.</a><br>
1.34 deraadt 23: <br>
1.35 deraadt 24: For errata on a certain release, click below:<br>
1.34 deraadt 25: <a href="errata21.html">2.1</a>,
26: <a href="errata23.html">2.3</a>,
27: <a href="errata24.html">2.4</a>,
28: <a href="errata25.html">2.5</a>,
29: <a href="errata26.html">2.6</a>,
30: <a href="errata27.html">2.7</a>,
31: <a href="errata28.html">2.8</a>,
32: <a href="errata29.html">2.9</a>,
33: <a href="errata30.html">3.0</a>,
34: <a href="errata31.html">3.1</a>,
1.38 deraadt 35: <a href="errata32.html">3.2</a>,
1.40 david 36: <a href="errata33.html">3.3</a>,
1.44 david 37: <a href="errata34.html">3.4</a>,
1.45 miod 38: <a href="errata35.html">3.5</a>,
1.46 deraadt 39: <a href="errata36.html">3.6</a>,
1.47 ! deraadt 40: <a href="errata37.html">3.7</a>,
! 41: <a href="errata.html">3.8</a>.
1.34 deraadt 42: <br>
1.2 deraadt 43: <hr>
44:
1.37 naddy 45: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2.tar.gz">
1.11 deraadt 46: You can also fetch a tar.gz file containing all the following patches</a>.
47: This file is updated once a day.
48:
1.21 ericj 49: <p>
1.36 deraadt 50: For more detailed information on how to install patches to OpenBSD, please
1.21 ericj 51: consult the <a href="./faq/faq10.html#10.14">OpenBSD FAQ</a>.
52:
1.11 deraadt 53: <hr>
54:
1.41 henning 55: <a name="all"></a>
56: <h3><font color="#e00000">All architectures</font></h3>
1.1 deraadt 57: <ul>
1.41 henning 58: <li><a name="ipsec"></a>
59: <font color="#009000"><strong>SECURITY FIX</strong></font><br>
1.7 deraadt 60: If IPSEC communication is attempted by starting photurisd(8) (which is
1.8 deraadt 61: disabled by default), a system crash may be evoked from remote if
62: an attacker uses some classes of invalid packets.
1.39 david 63: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/ipsec.patch">
1.7 deraadt 64: A source code patch exists which remedies this problem.</a>
1.9 deraadt 65: <p>
1.41 henning 66: <li><a name="xterm-xaw"></a>
67: <font color="#009000"><strong>SECURITY FIX</strong></font><br>
1.5 matthieu 68: As stated in CERT advisory VB-98.04, there are buffer
1.8 deraadt 69: overrun problems in <strong>xterm</strong> related to the input-Method,
70: preeditType, and *Keymap resources. Additional buffer overruns exist in
71: the <strong>Xaw</strong> library related to the inputMethod and
72: preeditType resources. The xterm(1) problem represents a security
73: vulnerability for any platform where xterm is installed setuid-root
74: (as is the case for all OpenBSD platforms). The Xaw problem represents
75: a security vulnerability for any setuid-root program that uses the Xaw
76: library (including xterm). Patch1 from XFree86 3.3.2 corrects
77: these problems.
1.37 naddy 78: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/xterm-xaw.patch">
1.6 deraadt 79: We provide a version of this patch file specifically for the OpenBSD 2.2 tree</a>.
1.5 matthieu 80: <p>
1.41 henning 81: <li><a name="rmjob"></a>
82: <font color="#009000"><strong>SECURITY FIX</strong></font><br>
1.1 deraadt 83: An exploitable buffer mismanagement exists in a subroutine used by
84: lprm and lpd. The problem is exploitable by users on a particular
85: machine if there is an entry in <strong>/etc/printcap</strong> which
86: points at a remote printer.
1.37 naddy 87: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/rmjob.patch">
1.1 deraadt 88: A patch is available which corrects this behaviour</a>.
89: <p>
1.41 henning 90: <li><a name="uucpd"></a>
91: <font color="#009000"><strong>SECURITY FIX</strong></font><br>
1.1 deraadt 92: A DNS-based vulnerability exists when uucpd is used. By default uucpd
93: is not enabled in the OpenBSD releases, but some sites may have enabled it.
1.37 naddy 94: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/uucpd.patch">
1.1 deraadt 95: A patch is available which corrects this behaviour</a>.
96: <p>
1.41 henning 97: <li><a name="named"></a>
98: <font color="#009000"><strong>SECURITY FIX</strong></font><br>
1.1 deraadt 99: A vulnerability exists when (and only when) /etc/named.conf has the
100: <strong>fake-iquery</strong> option enabled.
1.37 naddy 101: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/named.patch">
1.1 deraadt 102: A patch is available which corrects this behaviour</a>.
103: <p>
1.41 henning 104: <li><a name="ping"></a>
105: <font color="#009000"><strong>SECURITY FIX</strong></font><br>
1.1 deraadt 106: A vulnerability exists in ping(8); if the -R option is used to record
107: routes, an attacker can spoof a reply packet that will overflow inside
108: ping. Preliminary investigation makes it look the worst attack
109: possible is to make ping crash, but one never knows...
1.37 naddy 110: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/ping.patch">
1.1 deraadt 111: A patch is available which corrects this behaviour</a>.
112: <p>
1.41 henning 113: <li><a name="sourceroute"></a>
114: <strong><font color="#009000">SECURITY FIX</font></strong><br>
1.1 deraadt 115: If the sysctl variable <strong>net.inet.ip.forwarding</strong> is
116: enabled (value 1), but the variable <strong>net.inet.ip.sourceroute</strong>
117: is disabled (value 0), the kernel will block source routed packets from
118: going through, but will still accept source routing packets destined for
119: itself. Our fix changes the <strong>net.inet.ip.sourceroute</strong>
120: variable semantics to mean that all source routed packets should
121: be blocked completely.
1.37 naddy 122: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/sourceroute.patch">
1.1 deraadt 123: A kernel patch is provided</a>.
124: <p>
1.41 henning 125: <li><a name="ruserok"></a>
126: <font color="#009000"><strong>SECURITY FIX</strong></font><br>
1.1 deraadt 127: A combination localhost+remote host security problem exists if a
1.26 jsyn 128: local user running a setuid binary causes a non-existent root .rhosts
1.1 deraadt 129: file to be created via a symbolic link with a specific kind of corefile,
130: and then subsequently uses rsh/rlogin to enter the machine from remote.
131: A similar exploit might also be possible using sshd which lacks any code
132: for checking for deviations from the expected format in the .rhosts or
133: .shosts files, but we have not confirmed this yet. The following two
134: fixes are recommended:
135: <p>
136: <ul>
137: <li>
1.37 naddy 138: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/nosuidcoredump.patch">
1.1 deraadt 139: (1) A kernel patch which adds a new sysctl option which permits the
140: administrator to decide whether setuid corefiles should be written or not</a>.
141: <p>
1.37 naddy 142: <li><a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/rcmd.patch">
1.1 deraadt 143: (2) Replaces the libc ruserok() function with a more paranoid
144: version which detects bogus looking .rhosts files better.</a>
145: </ul>
146: <p>
147: If the
148: first patch is used to stop setuid coredumps, then the second patch is
149: not as important.
150: This problem is fixed much better in OpenBSD-current, where the kernel's
151: symbolic link handling has been improved such that coredumping will not
152: create a file on the other side of a symbolic link. Such a patch is not
153: possible for the 4.4lite1 VFS layer in the OpenBSD 2.2 kernel.<p>
154: The problem with the ruserok() function appears to also exist in
155: ssh 1.2.21 and previous (the ssh people have been alerted).
156: <p>
1.41 henning 157: <li><a name="mmap"></a>
158: <strong><font color="#009000">SECURITY FIX</font></strong><br>
1.1 deraadt 159: A bug in the vm system permits a file descriptor opened read-only on a
160: device, to later on be mmap(2)'d read-write, and then modified. This
161: does not result in a security hole by itself, but it does violate the
162: safety semantics which securelevels are supposed to provide. If a user
163: manages to gain kmem group permissions, using this problem they can then
164: gain root trivially and/or turn securelevels off.
1.37 naddy 165: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/vm_mmap.patch">
1.1 deraadt 166: A kernel patch is available which corrects this behaviour (this is
167: revision 3 of this patch)</a>.
168: <p>
1.37 naddy 169: <li><font color="#009000"><strong>BUILD PROCESS FIX</strong></font><br>
1.1 deraadt 170: Building an object tree from a read-only source tree (such as off a CDROM)
171: may fail under certain circumstances (e.g. when creating a symlink on sparc
172: whose target name is exactly 33 characters). As a workaround you have to
173: either provide the source tree read/write, or install a newer version of
174: /usr/bin/readlink.
1.37 naddy 175: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/readlink.c">
1.1 deraadt 176: A replacement source file exists</a>.
177: <p>
1.41 henning 178: <li><a name="mountd"></a>
179: <font color="#009000"><strong>SECURITY FIX</strong></font><br>
1.1 deraadt 180: If a line in /etc/exports which contains hostnames results in an empty
181: list because none of the supplied hostnames is known, mountd(8) will
182: accidentally export the filesystem to the world.
1.37 naddy 183: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/mountd.patch">
1.1 deraadt 184: A patch is available which corrects this behaviour</a>.
185: <p>
1.37 naddy 186: <li><font color="#009000"><strong>RELIABILITY FIX</strong></font><br>
1.1 deraadt 187: Setting the MSG_EOR flag on a tcp packet in the send(2) family of
188: system calls could cause a kernel panic.
1.37 naddy 189: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/common/send.patch">
1.1 deraadt 190: A patch</a> to return EINVAL in this case is available.
191: <p>
192: </ul>
1.41 henning 193: <a name="i386"></a>
194: <h3><font color="#e00000">i386</font></h3>
1.1 deraadt 195: <ul>
1.41 henning 196: <li><a name="f00f"></a>
197: <font color="#009000"><strong>RELIABILITY FIX</strong></font><br>
1.26 jsyn 198: The Intel P5 F00F bug was discovered after the CDRs had already been
1.1 deraadt 199: sent to the manufacturer. This problem permits any user who has an account
200: to lock your machine up using a 4-line program. The problem only affects
201: Intel P5 processors (the i386, i486, P-Pro, and P-II are not vulnerable,
202: nor are processors by other manufacturers).
1.37 naddy 203: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/i386/f00f.patch">
1.1 deraadt 204: A kernel source-code patch is available</a>.
205: <p>
1.37 naddy 206: <li><font color="#009000"><strong>FUNCTIONALITY FIX</strong></font><br>
1.1 deraadt 207: Some Linux binaries will execute in SVR4 emulation mode, which is
1.12 aaron 208: definitely a problem for people who need Linux emulation to work correctly.
1.1 deraadt 209: To solve this mis-identification problem,
1.37 naddy 210: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/i386/compat_linux.patch">
1.1 deraadt 211: a patch file is provided</a>.
212: <p>
1.37 naddy 213: <li><font color="#009000"><strong>RELIABILITY FIX</strong></font><br>
1.1 deraadt 214: APM can crash on machines without it.
1.37 naddy 215: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/i386/apm.patch">
1.1 deraadt 216: A kernel source-code patch is available</a>.
217: <p>
1.37 naddy 218: <li><font color="#009000"><strong>INSTALLATION PROCESS FLAW</strong></font><br>
1.25 pvalchev 219: A few people are running into this problem, particularly if they had some
1.1 deraadt 220: other *BSD operating system on their machine before trying OpenBSD: if after
221: installation onto an IDE-based machine, the kernel fails to mount the root
222: partition because it thinks that it should be opening sd0 (0x400), this means
223: you have incorrectly setup your disklabel for the IDE drive -- the disklabel
224: is indicating that the drive is SCSI.
225: To repair this, use the floppy to run "disklabel -E wd0", then using the
226: "edit" command ensure the type field is set to "ST506".
227: <p>
228: </ul>
1.41 henning 229: <a name="mac68k"></a>
230: <h3><font color="#e00000">mac68k</font></h3>
1.1 deraadt 231: <ul>
1.37 naddy 232: <li><font color="#009000"><strong>NEW SOFTWARE</strong></font><br>
1.1 deraadt 233: Unfortunately, X11 binaries for the mac68k did not manage to make it onto the
234: CDROM. However, X11 for the mac68k is immediately available from
235: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/2.2/mac68k/X11/X11R6.tar.gz">
236: ftp://ftp.OpenBSD.org/pub/OpenBSD/2.2/mac68k/X11/X11R6.tar.gz</a>. Please
237: 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
238: and setting up X.
239: <p>
1.37 naddy 240: <li><font color="#009000"><strong>INSTALLATION PROCESS FLAW</strong></font><br>
1.1 deraadt 241: As shipped on the CDROM, both the
242: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/2.2/mac68k/bsd-generic.tar.gz">
243: generic kernel</a>
244: and the
245: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/2.2/bsd-genericbsc.tar.gz">
246: genericsbc kernel</a>
247: extract themselves into the wrong place in the filesystem.
248: Both <strong>should</strong> extract a kernel named <tt>/bsd</tt>, but they extract
249: the kernel into <tt>/usr/src/sys/arch/mac68k/compile</tt> instead.
250: <p>
251: This has been fixed on the ftp release of <a href=22.html>OpenBSD 2.2</a>, and
252: fresh kernels are available from <a href="ftp://ftp.openbsd.org/pub/OpenBSD/2.2/mac68k">
253: ftp://ftp.OpenBSD.ORG/pub/OpenBSD/2.2/mac68k/</a>. If at all possible,
254: installing these kernels is recommended.
255: <p>
256: A number of possible workarounds exist if you don't have easy access to ftp
257: the updated kernels. The simplest of these is to use a
258: MacOS program to uncompress and untar the kernel aad use the Installer's
259: mini-shell to "cpin" the kernel. Alternately, you could install the kernel
260: with the Installer and use the mini-shell to move the binary from <tt>/usr/src/...</tt> to <tt>/bsd</tt>.
261: <p>
262: </ul>
1.41 henning 263: <a name="sparc"></a>
264: <h3><font color="#e00000">sparc</font></h3>
1.1 deraadt 265: <ul>
1.37 naddy 266: <li><font color="#009000"><strong>RELIABILITY FIX</strong></font><br>
1.25 pvalchev 267: Older 4/xxx systems (particularly the 4/300's) cannot boot
1.1 deraadt 268: with the 2.2 kernel due to bugs in the scsi device driver.
1.37 naddy 269: <a href="ftp://ftp.OpenBSD.org/pub/OpenBSD/patches/2.2/sparc/esp.patch">
1.1 deraadt 270: A kernel source patch is available</a>.
271: Replacement kernels are available for:
1.37 naddy 272: <a href="ftp://ftp.OpenBSD.org/pub/OpenBSD/patches/2.2/sparc/bsd">bsd</a>,
273: <a href="ftp://ftp.OpenBSD.org/pub/OpenBSD/patches/2.2/sparc/bsd.scsi3">bsd.scsi3</a>,
1.1 deraadt 274: and a replacement for bsd.rd is coming soon.
275: <p>
1.41 henning 276: <li><a name="sparciommu"></a>
277: <font color="#009000"><strong>RELIABILITY FIX</strong></font><br>
1.1 deraadt 278: SPARCstation 4 and 5 (Microsparc 2) users may see kernel panics when
279: using a custom kernel configured for option sun4m only.
1.37 naddy 280: <a href="ftp://ftp.OpenBSD.org/pub/OpenBSD/patches/2.2/sparc/sun4m.patch">
1.1 deraadt 281: A workaround (kernel source patch) is available</a>. Apply the patch and
282: then re-build your kernel.
283: <p>
284: </ul>
1.41 henning 285: <h3><font color="#e00000">amiga</font></h3>
1.1 deraadt 286: <p>
287: <ul>
1.37 naddy 288: <li><font color="#009000"><strong>FUNCTIONALITY FIX</strong></font><br>
1.1 deraadt 289: Missing Xamiga manual pages. Get
1.37 naddy 290: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/amiga/Xamiga-manual.tgz">
1.1 deraadt 291: this package</a> and execute, <i>as root</i>:<br>
292: <strong><b># </b>pkg_add Xamiga-manual.tgz</strong><br>
293: The MD5 checksum of this package is:<br>
294: <b>MD5 (Xamiga-manual.tgz) = 2362a7857264b9d17f65cca258b42031</b><p>
1.37 naddy 295: <li><font color="#009000"><strong>FUNCTIONALITY FIX</strong></font><br>
1.1 deraadt 296: The Ariadne ethernet support was broken, there will be both binary and
297: source level fixes available shortly. If you are in a hurry mail
1.37 naddy 298: <a href="mailto:niklas@openbsd.org">Niklas</a> for a test kernel.<p>
1.1 deraadt 299: </ul>
1.41 henning 300: <a name="pmax"></a>
301: <h3><font color="#e00000">pmax</font></h3>
1.1 deraadt 302: <ul>
1.37 naddy 303: <li><font color="#009000"><strong>FUNCTIONALITY FIX</strong></font><br>
1.1 deraadt 304: There is a Year-1998 problem in the time-setting code (which causes the
305: date and time to be set incorrectly after a reboot in 1998).
1.37 naddy 306: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/clock.patch">
1.1 deraadt 307: A source code patch file is available</a> plus replacement installation
308: kernels for the 2.2 release at
1.37 naddy 309: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/bsd.NFS">bsd.NFS</a>,
310: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/bsd">bsd</a>,
311: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/bsd.rz0">bsd.rz0</a>.
1.1 deraadt 312: <p>
1.37 naddy 313: <li><font color="#009000"><strong>FUNCTIONALITY FIX</strong></font><br>
1.1 deraadt 314: X11 support for the 3min and 3maxplus machines was broken
315: due to a kernel bug.
1.37 naddy 316: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/fb.patch">
1.1 deraadt 317: A source code patch is available</a>.
318: <p>
1.41 henning 319: <li><a name="ldso"></a>
320: <font color="#009000"><strong>SECURITY FIX</strong></font><br>
1.1 deraadt 321: A security problem in the shared library linker <strong>ld.so</strong>
322: requires that you replace it with a new binary. The following binary
323: will work on both pmax and arc machines.
1.37 naddy 324: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/ld.so">
1.1 deraadt 325: The replacement binary is here</a>.
326: <p>
327: </ul>
1.41 henning 328: <a name="arc"></a>
329: <h3><font color="#e00000">arc</font></h3>
1.1 deraadt 330: <ul>
1.37 naddy 331: <li><font color="#009000"><strong>SECURITY FIX</strong></font><br>
1.1 deraadt 332: A security problem in the shared library linker <strong>ld.so</strong> requires
333: that you replace it with a new binary. The following binary
334: will work on both pmax and arc machines.
1.37 naddy 335: <a href="ftp://ftp.openbsd.org/pub/OpenBSD/patches/2.2/pmax/ld.so">
1.1 deraadt 336: The replacement binary is here</a>.
337: <p>
338: </ul>
1.41 henning 339: <h3><font color="#e00000">alpha</font></h3>
1.1 deraadt 340: <p>
341: <ul>
1.37 naddy 342: <li><font color="#009000"><strong>MISSING FUNCTIONALITY</strong></font><br>
1.4 deraadt 343: Network Address Translation and other parts of IP Filtering do not work
1.1 deraadt 344: on the alpha. This will be fixed in the 2.3 release, and perhaps earlier
345: in a snapshot. There is no patch for 2.2.
346: <p>
347: </ul>
1.41 henning 348: <h3><font color="#e00000">hp300</font></h3>
1.1 deraadt 349: <p>
350: <ul>
351: <li>No problems identified yet.
352: <p>
353: </ul>
1.41 henning 354: <h3><font color="#e00000">mvme68k</font></h3>
1.1 deraadt 355: <ul>
356: <li>No problems identified yet.
357: <p>
358: </ul>
1.17 deraadt 359:
1.1 deraadt 360: <br>
361:
362: <hr>
1.20 jason 363: <a href=stable.html>For OpenBSD patch branch information, please refer here.</a><br>
1.34 deraadt 364: <br>
1.35 deraadt 365: For errata on a certain release, click below:<br>
1.34 deraadt 366: <a href="errata21.html">2.1</a>,
367: <a href="errata23.html">2.3</a>,
368: <a href="errata24.html">2.4</a>,
369: <a href="errata25.html">2.5</a>,
370: <a href="errata26.html">2.6</a>,
371: <a href="errata27.html">2.7</a>,
372: <a href="errata28.html">2.8</a>,
373: <a href="errata29.html">2.9</a>,
374: <a href="errata30.html">3.0</a>,
375: <a href="errata31.html">3.1</a>,
1.38 deraadt 376: <a href="errata32.html">3.2</a>,
1.40 david 377: <a href="errata33.html">3.3</a>,
1.44 david 378: <a href="errata34.html">3.4</a>,
1.45 miod 379: <a href="errata35.html">3.5</a>,
1.46 deraadt 380: <a href="errata36.html">3.6</a>,
1.47 ! deraadt 381: <a href="errata37.html">3.7</a>,
! 382: <a href="errata.html">3.8</a>.
1.34 deraadt 383: <br>
384:
1.1 deraadt 385: <hr>
1.16 deraadt 386: <a href=index.html><img height=24 width=24 src=back.gif border=0 alt=OpenBSD></a>
1.37 naddy 387: <a href="mailto:www@openbsd.org">www@openbsd.org</a>
1.47 ! deraadt 388: <br><small>$OpenBSD: errata22.html,v 1.46 2005/05/17 16:21:21 deraadt Exp $</small>
1.1 deraadt 389:
390: </body>
391: </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