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