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