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