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