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