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