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