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