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