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