Annotation of www/errata61.html, Revision 1.49
1.39 bentley 1: <!doctype html>
2: <html lang=en id=errata>
3: <meta charset=utf-8>
4:
1.1 tj 5: <title>OpenBSD 6.1 Errata</title>
6: <meta name="description" content="the OpenBSD errata page">
7: <meta name="viewport" content="width=device-width, initial-scale=1">
8: <link rel="stylesheet" type="text/css" href="openbsd.css">
9: <link rel="canonical" href="https://www.openbsd.org/errata61.html">
10:
11: <!--
12: IMPORTANT REMINDER
13: IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE
14: -->
15:
1.39 bentley 16: <h2 id=OpenBSD>
1.1 tj 17: <a href="index.html">
1.39 bentley 18: <i>Open</i><b>BSD</b></a>
19: 6.1 Errata
1.1 tj 20: </h2>
21: <hr>
22:
23: For errata on a certain release, click below:<br>
1.41 schwarze 24: <a href="errata20.html">2.0</a>,
1.1 tj 25: <a href="errata21.html">2.1</a>,
26: <a href="errata22.html">2.2</a>,
27: <a href="errata23.html">2.3</a>,
28: <a href="errata24.html">2.4</a>,
29: <a href="errata25.html">2.5</a>,
30: <a href="errata26.html">2.6</a>,
31: <a href="errata27.html">2.7</a>,
32: <a href="errata28.html">2.8</a>,
33: <a href="errata29.html">2.9</a>,
34: <a href="errata30.html">3.0</a>,
35: <a href="errata31.html">3.1</a>,
36: <a href="errata32.html">3.2</a>,
37: <a href="errata33.html">3.3</a>,
38: <a href="errata34.html">3.4</a>,
39: <a href="errata35.html">3.5</a>,
1.41 schwarze 40: <br>
1.1 tj 41: <a href="errata36.html">3.6</a>,
42: <a href="errata37.html">3.7</a>,
43: <a href="errata38.html">3.8</a>,
44: <a href="errata39.html">3.9</a>,
45: <a href="errata40.html">4.0</a>,
46: <a href="errata41.html">4.1</a>,
47: <a href="errata42.html">4.2</a>,
48: <a href="errata43.html">4.3</a>,
49: <a href="errata44.html">4.4</a>,
50: <a href="errata45.html">4.5</a>,
51: <a href="errata46.html">4.6</a>,
52: <a href="errata47.html">4.7</a>,
53: <a href="errata48.html">4.8</a>,
54: <a href="errata49.html">4.9</a>,
55: <a href="errata50.html">5.0</a>,
56: <a href="errata51.html">5.1</a>,
1.41 schwarze 57: <br>
1.1 tj 58: <a href="errata52.html">5.2</a>,
59: <a href="errata53.html">5.3</a>,
60: <a href="errata54.html">5.4</a>,
61: <a href="errata55.html">5.5</a>,
62: <a href="errata56.html">5.6</a>,
63: <a href="errata57.html">5.7</a>,
64: <a href="errata58.html">5.8</a>,
65: <a href="errata59.html">5.9</a>,
1.23 deraadt 66: <a href="errata60.html">6.0</a>,
1.34 deraadt 67: <a href="errata62.html">6.2</a>,
1.37 deraadt 68: <a href="errata63.html">6.3</a>,
1.38 deraadt 69: <a href="errata64.html">6.4</a>,
1.40 deraadt 70: <a href="errata65.html">6.5</a>,
1.42 deraadt 71: <a href="errata66.html">6.6</a>,
1.43 deraadt 72: <a href="errata67.html">6.7</a>,
1.44 deraadt 73: <a href="errata68.html">6.8</a>,
1.45 tj 74: <br>
1.46 deraadt 75: <a href="errata69.html">6.9</a>,
1.47 deraadt 76: <a href="errata70.html">7.0</a>,
1.48 deraadt 77: <a href="errata71.html">7.1</a>,
1.49 ! tj 78: <a href="errata72.html">7.2</a>,
! 79: <a href="errata73.html">7.3</a>.
1.1 tj 80: <hr>
81:
82: <p>
83: Patches for the OpenBSD base system are distributed as unified diffs.
84: Each patch is cryptographically signed with the
1.15 tb 85: <a href="https://man.openbsd.org/OpenBSD-6.1/signify.1">signify(1)</a> tool and contains
1.1 tj 86: usage instructions.
87: All the following patches are also available in one
88: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1.tar.gz">tar.gz file</a>
89: for convenience.
90:
91: <p>
1.32 tj 92: Alternatively, the <a href="https://man.openbsd.org/syspatch">syspatch(8)</a>
93: utility can be used to apply binary updates on the following architectures:
1.35 tj 94: amd64, i386.
1.32 tj 95:
96: <p>
1.1 tj 97: Patches for supported releases are also incorporated into the
1.35 tj 98: <a href="stable.html">-stable branch</a>.
1.1 tj 99:
100: <hr>
101:
102: <ul>
103:
1.4 tj 104: <li id="p001_dhcpd">
1.39 bentley 105: <strong>001: INTEROPERABILITY FIX: May 2, 2017</strong>
1.4 tj 106: <i>All architectures</i>
107: <br>
108: dhcpd unconditionally echoed the client identifier, preventing some devices
1.5 tb 109: from acquiring a lease.
1.4 tj 110: <br>
111: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/001_dhcpd.patch.sig">
112: A source code patch exists which remedies this problem.</a>
113: <p>
114:
115: <li id="p002_vmmfpu">
1.39 bentley 116: <strong>002: SECURITY FIX: May 2, 2017</strong>
1.6 mlarkin 117: <i>amd64</i>
1.4 tj 118: <br>
119: vmm mismanaged floating point contexts.
120: <br>
121: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/002_vmmfpu.patch.sig">
122: A source code patch exists which remedies this problem.</a>
123: <p>
124:
125: <li id="p003_libressl">
1.39 bentley 126: <strong>003: SECURITY FIX: May 2, 2017</strong>
1.4 tj 127: <i>All architectures</i>
128: <br>
129: A consistency check error could cause programs to incorrectly verify
130: TLS certificates when using callbacks that always return 1.
131: <br>
132: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/003_libressl.patch.sig">
133: A source code patch exists which remedies this problem.</a>
134: <p>
135:
136: <li id="p004_softraid_concat">
1.39 bentley 137: <strong>004: RELIABILITY FIX: May 2, 2017</strong>
1.4 tj 138: <i>All architectures</i>
139: <br>
140: softraid was unable to create usable concat volumes because
141: it always set the size of the volume to zero sectors.
142: <br>
143: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/004_softraid_concat.patch.sig">
144: A source code patch exists which remedies this problem.</a>
145: <p>
1.1 tj 146:
1.7 tj 147: <li id="p005_pf_src_tracking">
1.39 bentley 148: <strong>005: RELIABILITY FIX: May 6, 2017</strong>
1.7 tj 149: <i>All architectures</i>
150: <br>
151: Expired pf source tracking entries never got removed, leading to
152: memory exhaustion.
153: <br>
154: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/005_pf_src_tracking.patch.sig">
155: A source code patch exists which remedies this problem.</a>
156: <p>
157:
1.8 tj 158: <li id="p006_libssl">
1.39 bentley 159: <strong>006: RELIABILITY FIX: May 8, 2017</strong>
1.8 tj 160: <i>All architectures</i>
161: <br>
162: Incorrect DTLS cookie handling can result in a NULL pointer dereference.
163: <br>
164: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/006_libssl.patch.sig">
165: A source code patch exists which remedies this problem.</a>
166: <p>
167:
1.9 tj 168: <li id="p007_freetype">
1.39 bentley 169: <strong>007: SECURITY FIX: May 13, 2017</strong>
1.9 tj 170: <i>All architectures</i>
171: <br>
172: Heap-based buffer overflows in freetype can result in out-of-bounds writes.
173: <br>
174: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/007_freetype.patch.sig">
175: A source code patch exists which remedies this problem.</a>
176: <p>
177:
1.11 tj 178: <li id="p008_exec_subr">
1.39 bentley 179: <strong>008: SECURITY FIX: May 19, 2017</strong>
1.11 tj 180: <i>All architectures</i>
181: <br>
182: An additional mitigation is added by placing a gap of 1 MB between the
183: stack and mmap spaces.
184: <br>
185: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/008_exec_subr.patch.sig">
186: A source code patch exists which remedies this problem.</a>
187: <p>
188:
1.12 tj 189: <li id="p009_icmp_opts">
1.39 bentley 190: <strong>009: RELIABILITY FIX: May 22, 2017</strong>
1.12 tj 191: <i>All architectures</i>
192: <br>
1.14 tj 193: The kernel could leak memory when processing ICMP packets with IP options.
1.12 tj 194: Note that pf blocks such packets by default.
195: <br>
196: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/009_icmp_opts.patch.sig">
197: A source code patch exists which remedies this problem.</a>
198: <p>
199:
1.13 tj 200: <li id="p010_perl">
1.39 bentley 201: <strong>010: SECURITY FIX: June 4, 2017</strong>
1.13 tj 202: <i>All architectures</i>
203: <br>
204: A race condition exists in the File::Path perl module.
205: <br>
206: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/010_perl.patch.sig">
1.14 tj 207: A source code patch exists which remedies this problem.</a>
208: <p>
209:
210: <li id="p011_sti">
1.39 bentley 211: <strong>011: SECURITY FIX: June 12, 2017</strong>
1.14 tj 212: <i>hppa</i>
213: <br>
214: An integer overflow exists in two range checks of the sti(4) display driver.
215: <br>
216: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/011_sti.patch.sig">
217: A source code patch exists which remedies this problem.</a>
218: <p>
219:
220: <li id="p012_wsmux">
1.39 bentley 221: <strong>012: RELIABILITY FIX: June 12, 2017</strong>
1.14 tj 222: <i>All architectures</i>
223: <br>
224: An unprivileged user can cause a kernel crash.
225: <br>
226: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/012_wsmux.patch.sig">
1.13 tj 227: A source code patch exists which remedies this problem.</a>
228: <p>
229:
1.16 tj 230: <li id="p013_icmp6_linklocal">
1.39 bentley 231: <strong>013: RELIABILITY FIX: June 27, 2017</strong>
1.16 tj 232: <i>All architectures</i>
233: <br>
234: When pinging an IPv6 link-local address, the reflected packet had
235: ::1 as source address. The echo reply was ignored as it must be
236: from the link-local address.
237: <br>
238: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/013_icmp6_linklocal.patch.sig">
239: A source code patch exists which remedies this problem.</a>
240: <p>
241:
1.17 tj 242: <li id="p014_libcrypto">
1.39 bentley 243: <strong>014: RELIABILITY FIX: July 5, 2017</strong>
1.17 tj 244: <i>All architectures</i>
245: <br>
246: Self-issued certificates are improperly treated as self-signed certificates,
247: leading to possible verification failures.
248: <br>
249: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/014_libcrypto.patch.sig">
250: A source code patch exists which remedies this problem.</a>
251: <p>
252:
1.18 tj 253: <li id="p015_sigio">
1.39 bentley 254: <strong>015: RELIABILITY FIX: August 3, 2017</strong>
1.18 tj 255: <i>All architectures</i>
256: <br>
257: A SIGIO-related use-after-free can occur in two drivers.
258: <br>
259: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/015_sigio.patch.sig">
260: A source code patch exists which remedies this problem.</a>
261: <p>
262:
263: <li id="p016_sendsyslog">
1.39 bentley 264: <strong>016: RELIABILITY FIX: August 3, 2017</strong>
1.18 tj 265: <i>All architectures</i>
266: <br>
267: A missing length check in sendsyslog() may result in a kernel panic.
268: <br>
269: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/016_sendsyslog.patch.sig">
270: A source code patch exists which remedies this problem.</a>
271: <p>
272:
273: <li id="p017_fuse">
1.39 bentley 274: <strong>017: SECURITY FIX: August 3, 2017</strong>
1.18 tj 275: <i>All architectures</i>
276: <br>
277: An out-of-bound read in vfs_getcwd_scandir() (mainly used for FUSE)
278: may result in a kernel panic or info leak.
279: <br>
280: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/017_fuse.patch.sig">
281: A source code patch exists which remedies this problem.</a>
282: <p>
283:
284: <li id="p018_recv">
1.39 bentley 285: <strong>018: SECURITY FIX: August 3, 2017</strong>
1.18 tj 286: <i>All architectures</i>
287: <br>
288: An alignment issue in recv() may result in an info leak via ktrace().
289: <br>
290: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/018_recv.patch.sig">
291: A source code patch exists which remedies this problem.</a>
292: <p>
293:
294: <li id="p019_tcp_usrreq">
1.39 bentley 295: <strong>019: SECURITY FIX: August 3, 2017</strong>
1.18 tj 296: <i>All architectures</i>
297: <br>
298: With an invalid address family, tcp_usrreq() may take an unintended code path.
299: <br>
300: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/019_tcp_usrreq.patch.sig">
301: A source code patch exists which remedies this problem.</a>
302: <p>
303:
304: <li id="p020_sockaddr">
1.39 bentley 305: <strong>020: SECURITY FIX: August 3, 2017</strong>
1.18 tj 306: <i>All architectures</i>
307: <br>
308: Missing socket address validation from userland may result in an info leak.
309: <br>
310: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/020_sockaddr.patch.sig">
311: A source code patch exists which remedies this problem.</a>
312: <p>
313:
314: <li id="p021_ptrace">
1.39 bentley 315: <strong>021: SECURITY FIX: August 3, 2017</strong>
1.18 tj 316: <i>All architectures</i>
317: <br>
318: An uninitialized variable in ptrace() may result in an info leak.
319: <br>
320: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/021_ptrace.patch.sig">
321: A source code patch exists which remedies this problem.</a>
322: <p>
323:
324: <li id="p022_fcntl">
1.39 bentley 325: <strong>022: SECURITY FIX: August 3, 2017</strong>
1.18 tj 326: <i>All architectures</i>
327: <br>
328: An uninitialized variable in fcntl() may result in an info leak.
329: <br>
330: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/022_fcntl.patch.sig">
331: A source code patch exists which remedies this problem.</a>
332: <p>
333:
334: <li id="p023_wsdisplay">
1.39 bentley 335: <strong>023: RELIABILITY FIX: August 3, 2017</strong>
1.18 tj 336: <i>All architectures</i>
337: <br>
338: An integer overflow in wsdisplay_cfg_ioctl() may result in an out-of-bounds
339: read.
340: <br>
341: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/023_wsdisplay.patch.sig">
342: A source code patch exists which remedies this problem.</a>
343: <p>
344:
345: <li id="p024_sosplice">
1.39 bentley 346: <strong>024: SECURITY FIX: August 3, 2017</strong>
1.18 tj 347: <i>All architectures</i>
348: <br>
349: A race condition in sosplice() may result in a kernel memory leak.
350: <br>
351: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/024_sosplice.patch.sig">
352: A source code patch exists which remedies this problem.</a>
353: <p>
354:
355: <li id="p025_ieee80211">
1.39 bentley 356: <strong>025: SECURITY FIX: August 3, 2017</strong>
1.18 tj 357: <i>All architectures</i>
358: <br>
359: An out of bounds read could occur during processing of EAPOL frames in
360: the wireless stack. Information from kernel memory could be leaked to
361: root in userland via an ieee80211(9) ioctl.
362: <br>
363: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/025_ieee80211.patch.sig">
364: A source code patch exists which remedies this problem.</a>
365: <p>
366:
1.19 tj 367: <li id="p026_smap">
1.39 bentley 368: <strong>026: SECURITY FIX: August 26, 2017</strong>
1.19 tj 369: <i>amd64 and i386</i>
370: <br>
371: SMAP enforcement could be bypassed by userland code.
372: <br>
373: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/026_smap.patch.sig">
374: A source code patch exists which remedies this problem.</a>
375: <p>
376:
1.20 tj 377: <li id="p027_net80211_replay">
1.39 bentley 378: <strong>027: SECURITY FIX: August 30, 2017</strong>
1.20 tj 379: <i>All architectures</i>
380: <br>
381: State transition errors could cause reinstallation of old WPA keys.
382: <br>
383: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/027_net80211_replay.patch.sig">
384: A source code patch exists which remedies this problem.</a>
385: <p>
386:
1.21 tj 387: <li id="p028_perl">
1.39 bentley 388: <strong>028: SECURITY FIX: September 22, 2017</strong>
1.21 tj 389: <i>All architectures</i>
390: <br>
391: A buffer over-read and heap overflow in perl's regexp may result in
392: a crash or memory leak.
393: <br>
394: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/028_perl.patch.sig">
395: A source code patch exists which remedies this problem.</a>
396: <p>
397:
1.22 tj 398: <li id="p029_tcb">
1.39 bentley 399: <strong>029: RELIABILITY FIX: September 27, 2017</strong>
1.22 tj 400: <i>amd64</i>
401: <br>
402: Out of bounds TCB settings may result in a kernel panic.
403: <br>
404: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/029_tcb.patch.sig">
405: A source code patch exists which remedies this problem.</a>
406: <p>
407:
1.24 tj 408: <li id="p030_xrstor">
1.39 bentley 409: <strong>030: RELIABILITY FIX: October 4, 2017</strong>
1.24 tj 410: <i>amd64</i>
411: <br>
412: An unprivileged user can cause a kernel crash.
413: <br>
414: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/030_xrstor.patch.sig">
415: A source code patch exists which remedies this problem.</a>
416: <p>
417:
1.25 tj 418: <li id="p031_xrstor_resume">
1.39 bentley 419: <strong>031: SECURITY FIX: October 4, 2017</strong>
1.25 tj 420: <i>amd64</i>
421: <br>
422: A kernel executable address was leaked to userland.
423: <br>
1.26 tj 424: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/031_xrstor_resume.patch.sig">
1.25 tj 425: A source code patch exists which remedies this problem.</a>
426: <p>
427:
1.27 bluhm 428: <li id="p032_tcb_invalid">
1.39 bentley 429: <strong>032: RELIABILITY FIX: October 13, 2017</strong>
1.27 bluhm 430: <i>amd64</i>
431: <br>
432: A local user could trigger a kernel panic by using an invalid TCB value.
433: <br>
434: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/032_tcb_invalid.patch.sig">
435: A source code patch exists which remedies this problem.</a>
436: <p>
437:
1.29 tj 438: <li id="p033_mpls">
1.39 bentley 439: <strong>033: RELIABILITY FIX: December 10, 2017</strong>
1.29 tj 440: All architectures
441: <br>
442: A number of bugs were discovered in the MPLS stack that can be used to
443: remotely trigger a kernel panic.
444: <br>
445: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/033_mpls.patch.sig">
446: A source code patch exists which remedies this problem.</a>
447: <p>
448:
1.30 tj 449: <li id="p034_ahopts">
1.39 bentley 450: <strong>034: RELIABILITY FIX: February 2, 2018</strong>
1.30 tj 451: <i>All architectures</i>
452: <br>
453: Specially crafted IPsec AH packets with IP options or IPv6 extension
454: headers could crash or hang the kernel.
455: <br>
456: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/034_ahopts.patch.sig">
457: A source code patch exists which remedies this problem.</a>
458: <p>
459:
460: <li id="p035_prevhdr">
1.39 bentley 461: <strong>035: RELIABILITY FIX: February 2, 2018</strong>
1.30 tj 462: <i>All architectures</i>
463: <br>
464: Processing IPv6 fragments could incorrectly access memory of an mbuf
465: chain that is not within an mbuf. This may crash the kernel.
466: <br>
467: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/035_prevhdr.patch.sig">
468: A source code patch exists which remedies this problem.</a>
469: <p>
470:
471: <li id="p036_etherip">
1.39 bentley 472: <strong>036: SECURITY FIX: February 2, 2018</strong>
1.30 tj 473: <i>All architectures</i>
474: <br>
475: If the EtherIP tunnel protocol was disabled, IPv6 packets were not
476: discarded properly. This causes a double free in the kernel.
477: <br>
478: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/036_etherip.patch.sig">
479: A source code patch exists which remedies this problem.</a>
480: <p>
481:
1.31 tj 482: <li id="p037_meltdown">
1.39 bentley 483: <strong>037: SECURITY FIX: March 1, 2018</strong>
1.31 tj 484: <i>amd64</i>
485: <br>
486: Intel CPUs contain a speculative execution flaw called Meltdown which
487: allows userspace programs to access kernel memory.
488: <br>
489: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/037_meltdown.patch.sig">
490: A complex workaround solves the problem.</a>
491: <p>
492:
1.33 tj 493: <li id="p038_ahauth">
1.39 bentley 494: <strong>038: RELIABILITY FIX: March 20, 2018</strong>
1.33 tj 495: <i>All architectures</i>
496: <br>
497: The IPsec AH header could be longer than the network packet, resulting in
498: a kernel crash.
499: <br>
500: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/038_ahauth.patch.sig">
501: A source code patch exists which remedies this problem.</a>
502: <p>
503:
1.36 afresh1 504: <li id="p039_perl">
1.39 bentley 505: <strong>039: SECURITY FIX: April 14, 2018</strong>
1.36 afresh1 506: <i>All architectures</i>
507: <br>
508: Heap overflows exist in perl which can lead to segmentation faults,
509: crashes, and reading memory past the buffer.
510: <br>
511: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/039_perl.patch.sig">
512: A source code patch exists which remedies this problem.</a>
513: <p>
514:
1.1 tj 515: </ul>
516:
517: <hr>
![[BACK]](/icons/back.gif){kind=icon}
Return to errata61.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www