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