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