1 .. -*- coding: utf-8-with-signature -*-
3 ==================================
4 User-Visible Changes in Tahoe-LAFS
5 ==================================
7 Release 1.10.1 (XXXX-XX-XX)
8 '''''''''''''''''''''''''''
10 Unedited list of all changes after 1.10.0 and up-to 143af61 17-May-2015. This
11 list is not yet limited to user-visible ones. It (hopefully) includes all
12 tickets closed during this time, even minor non-user-visible ones.
14 - show git branch in version output #1953
15 - packaging fixes #1969 #1960
16 - mutable/retrieve: raise NotEnoughSharesError earlier when the sharemap says
17 it's useless, and improve the error message #1742
18 - improve user feedback when filing an Incident Report #1974
19 - add page-rendering timestamp to WUI #1972
20 - improve what-is-my-ipv4 on windows/cygwin #1381
21 - remove unused 'human encoding' URI methods #1807
22 - check/deep-check learned to accept multiple location args #740
23 - tests warn if tree is dirty #1992
24 - Travis-CI turned on #2249
25 - py2.6 is now unsupported on windows
26 - add 'distclean', don't remove egg-info during 'make clean' #2092
27 - add "UTF-8 BOM" to all docs #1948
28 - various docs cleanups/improvements
29 - improve safety of timing_safe_compare() #2165
30 - checker reports: remove needs-rebalancing, add count-happiness #1784 #2105
31 - improve packaging under pip #2209
32 - remove old darcs tooling
33 - minor comments #1874 #2086
34 - switch to unminified d3/jquery JS files #2208
36 - reject furlfiles with "#" #2128
37 - rename exit-trigger/self-destruct test feature #1336
38 - add coverage.io test-coverage reporting #623
39 - hush warnings during dep-checking, stop complaining about missing
40 "service_identity" dep #2248
41 - dedup license info in about.rst/README.txt #2067
42 - 'tahoe cp -r' copies the top-level directory into new dir #712
43 - log roothash in base32 not binary #1800
44 - improve welcome page CSS for narrow windows #1931
45 - redesign WUI directory pages #1966
46 - improve upload tests #2008
47 - remove obsolete debian packaging tools #2282
48 - add --coverage to setup.py test #1698, remove old coverage uploaders
49 - remove trialcoverage plugin #2281
50 - tolerate disk-space-used=0 for travis boxes #2290
51 - tolerate python subprocess bug #2023
52 - remove old build_helpers tools #2305
53 - fix "Download" button on welcome page #1901
55 - hack windows/OpenSSL deps on windows #2249 #2193
56 - WAPI: do not report 'size' metadata when unknown #1634
57 - new OS-X packaging #182
58 - stop using contents of .tac files #1159
59 - improve version-number reporting #2340
60 - add per-server "(space) Available" column to welcome page #648
61 - add public-key auth to SFTP server #1411
62 - `tahoe cp -r` changes w.r.t. unnamed directories #2329
63 - tolerate PEP440 semantics in dependency specifications #2354
64 - replace WUI icons with distinct shapes for accessibility #1961
65 - hush DeprecationWarning with twisted.web #2312
66 - fix race condition during mutable upload
67 - fix handling of long paths on windows #2235 #1674 #2027
68 - fix MANIFEST.in warnings #2380
69 - use "AUTO" in tahoe.cfg/node/tub.location to mean autodetect IP addresses.
70 Can be combined with static addresses, or turned off entirely. #754
71 - 'tahoe cp -r': fix exception #2329
72 - put version string into name of OS-X package: #2393
73 - improve unicode handling of arguments to (S)FTPServer #2388
74 - improve tests of test_mutable #2034
75 - fix ftp 'ls' to work with Twisted-15.0.0 #2394
76 - add docs/proposed/magic-folder
77 - remove named-path upload/download from control-port #1737
78 - unicode handling on windows something #2398
79 - depend on foolscap >= 0.8.0, which makes better keys #2400
80 - zetuptoolz: tolerate single-string requirespec #2242
81 - add icon for OS-X/windows #2323
82 - initial Docker support PR#165
83 - accept newer Twisted (>=13) on windows if pywin32 is manually installed #2416
84 - windows: find home directory on multiple versions of windows #2417
85 - improve fileutil something #1531
87 all tickets noted as closed: 1953 1960 1974 1972 1717 1381 898 1707 1918 1807
88 740 1842 1992 2165 1847 2086 2208 2048 2128 2245 1336 2248 2067 712 1800 1966
89 2008 2282 2281 2290 2023 2121? 2305 1901 2249 2193 1634 1159 2340 1146 648
90 1411 2354 1961 2380 754 2393 2394 1737 2398 2400 2242 2416 2415 2417
92 all tickets referenced (fixed? not fixed?): 1834 1969 1742 1988 982 1064 1536
93 1935 666 1784 2105 2209 2280 623 2249 1931 1698 2028 2005 1258 182 2312 2235
94 1674 2027 2034 2323 2286 1531
96 PRs noted as closed: 62 48 57 61 62 63 64 69 73 81 82 84 85 87 91 94 95 96
97 103 56 32 50 107 109 114 112 120 122 125 126 133 135 136 137 142 146 149 152 165
101 There are many "cp"-like tools in the unix world (POSIX /bin/cp, the "scp"
102 provided by SSH, rsync). They each behave slightly differently in unusual
103 circumstances, generally dealing with copying whole directories at a time,
104 into a target which may or may not exist already. The usual question is
105 whether the user is referring to the source directory as a whole, or to its
106 contents. For example, should "cp -r foodir bardir" create a new directory
107 named "bardir/foodir"? Or should it behave more like "cp -r foodir/* bardir"?
108 Some tools use the presence of a trailing slash to indicate which behavior
109 you want. Others ignore trailing slashes.
111 "tahoe cp" is no exception to having exceptional cases. This release fixes
112 some bad behavior and attempts to establish a consistent rationale for its
117 - If the thing being copied is a directory, and it has a name (e.g. it's not
118 a raw tahoe directorycap), then you are referring to the directory itself.
119 - If the thing being copied is an unnamed directory (e.g. raw dircap or
120 alias), then you are referring to the contents.
121 - Trailing slashes do not affect the behavior of the copy (although putting a
122 trailing slash on a file-like target is an error).
123 - The "-r" (--recursive) flag does not affect the behavior of the copy
124 (although omitting -r when the source is a directory is an error).
125 - If the target refers to something that does not yet exist:
126 - and if the source is a single file, then create a new file;
127 - otherwise, create a directory.
129 There are two main cases where the behavior of tahoe-1.10.1 differs from that
130 of the 1.10.0 release:
132 - "cp DIRCAP/file.txt ./local/missing" , where "./local" is a directory but
133 "./local/missing" does not exist. The implication is that you want tahoe to
134 create a new file named "./local/missing" and fill it with the contents of
135 the tahoe-side DIRCAP/file.txt. In 1.10.0, a plain "cp" would do just this,
136 but "cp -r" would do "mkdir ./local/missing" and then create a file named
137 "./local/missing/file.txt". In 1.10.1, both "cp" and "cp -r" create a file
138 named "./local/missing".
139 - "cp -r PARENTCAP/dir ./local/missing", where PARENTCAP/dir/ contains
140 "file.txt", and again "./local" is a directory but "./local/missing" does
141 not exist. In both 1.10.0 and 1.10.1, this first does "mkdir
142 ./local/missing". In 1.10.0, it would then copy the contents of the source
143 directory into the new directory, resulting in "./local/missing/file.txt".
144 In 1.10.1, following the new rule of "a named directory source refers to
145 the directory itself", the tool creates "./local/missing/dir/file.txt".
148 Compatibility and Dependency Updates
149 ------------------------------------
155 - characteristic >= 14.0.0
157 - pyasn1-modules >= 0.0.5
159 On Windows, if pywin32 is not installed then the dependencies on Twisted
162 - Twisted >= 11.1.0, <= 12.1.0
163 - Nevow >= 0.9.33, <= 0.10
165 On all platforms, if pyOpenSSL >= 0.14 is installed, then it will be used,
166 but if not then only pyOpenSSL >= 0.13, <= 0.13.1 will be built when directly
167 invoking `setup.py build` or `setup.py install`.
169 We strongly advise OS packagers to take the option of making a tahoe-lafs
170 package depend on pyOpenSSL >= 0.14. In order for that to work, the following
171 additional Python dependencies are needed:
179 as well as libffi (for Debian/Ubuntu, the name of the needed OS package is
182 Tahoe-LAFS is now compatible with setuptools version 8 and pip version 6
186 Release 1.10.0 (2013-05-01)
187 '''''''''''''''''''''''''''
192 - The Welcome page has been redesigned. This is a preview of the design style
193 that is likely to be used in other parts of the WUI in future Tahoe-LAFS
194 versions. (`#1713`_, `#1457`_, `#1735`_)
195 - A new extensible Introducer protocol has been added, as the basis for
196 future improvements such as accounting. Compatibility with older nodes is
197 not affected. When server, introducer, and client are all upgraded, the
198 welcome page will show node IDs that start with "v0-" instead of the old
199 tubid. See `<docs/nodekeys.rst>`__ for details. (`#466`_)
200 - The web-API has a new ``relink`` operation that supports directly moving
201 files between directories. (`#1579`_)
203 Security Improvements
204 ---------------------
206 - The ``introducer.furl`` for new Introducers is now unguessable. In previous
207 releases, this FURL used a predictable swissnum, allowing a network
208 eavesdropper who observes any node connecting to the Introducer to access
209 the Introducer themselves, and thus use servers or offer storage service to
210 clients (i.e. "join the grid"). In the new code, the only way to join a
211 grid is to be told the ``introducer.furl`` by someone who already knew it.
212 Note that pre-existing introducers are not changed. To force an introducer
213 to generate a new FURL, delete the existing ``introducer.furl`` file and
214 restart it. After doing this, the ``[client]introducer.furl`` setting of
215 every client and server that should connect to that introducer must be
216 updated. Note that other users of a shared machine may be able to read
217 ``introducer.furl`` from your ``tahoe.cfg`` file unless you configure the
218 file permissions to prevent them. (`#1802`_)
219 - Both ``introducer.furl`` and ``helper.furl`` are now censored from the
220 Welcome page, to prevent users of your gateway from learning enough to
221 create gateway nodes of their own. For existing guessable introducer
222 FURLs, the ``introducer`` swissnum is still displayed to show that a
223 guessable FURL is in use. (`#860`_)
225 Command-line Syntax Changes
226 ---------------------------
228 - Global options to ``tahoe``, such as ``-d``/``--node-directory``, must now
229 come before rather than after the command name (for example,
230 ``tahoe -d BASEDIR cp -r foo: bar:`` ). (`#166`_)
235 - In earlier versions, if a connection problem caused a download failure for
236 an immutable file, subsequent attempts to download the same file could also
237 fail. This is now fixed. (`#1679`_)
238 - Filenames in WUI directory pages are now displayed correctly when they
239 contain characters that require HTML escaping. (`#1143`_)
240 - Non-ASCII node nicknames no longer cause WUI errors. (`#1298`_)
241 - Checking a LIT file using ``tahoe check`` no longer results in an
242 exception. (`#1758`_)
243 - The SFTP frontend now works with recent versions of Twisted, rather than
244 giving errors or warnings about use of ``IFinishableConsumer``. (`#1926`_,
246 - ``tahoe cp --verbose`` now counts the files being processed correctly.
248 - Exceptions no longer trigger an unhelpful crash reporter on Ubuntu 12.04
249 ("Precise") or later. (`#1746`_)
250 - The error message displayed when a CLI tool cannot connect to a gateway has
251 been improved. (`#974`_)
252 - Other minor fixes: `#1781`_, `#1812`_, `#1915`_, `#1484`_, `#1525`_
254 Compatibility and Dependencies
255 ------------------------------
257 - Python >= 2.6, except Python 3 (`#1658`_)
258 - Twisted >= 11.0.0 (`#1771`_)
259 - mock >= 0.8 (for unit tests)
260 - pycryptopp >= 0.6.0 (for Ed25519 signatures)
261 - zope.interface >= 3.6.0 (except 3.6.3 or 3.6.4)
266 - The ``flogtool`` utility, used to read detailed event logs, can now be
267 accessed as ``tahoe debug flogtool`` even when Foolscap is not installed
268 system-wide. (`#1693`_)
269 - The provisioning/reliability pages were removed from the main client's web
270 interface, and moved into a standalone web-based tool. Use the ``run.py``
271 script in ``misc/operations_helpers/provisioning/`` to access them.
272 - Web clients can now cache (ETag) immutable directory pages. (`#443`_)
273 - `<docs/convergence_secret.rst>`__ was added to document the adminstration
274 of convergence secrets. (`#1761`_)
276 Precautions when Upgrading
277 --------------------------
279 - When upgrading a grid from a recent revision of trunk, follow the
280 precautions from this `message to the tahoe-dev mailing list`_, to ensure
281 that announcements to the Introducer are recognized after the upgrade.
282 This is not necessary when upgrading from a previous release like 1.9.2.
284 .. _`#166`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/166
285 .. _`#443`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/443
286 .. _`#466`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/466
287 .. _`#860`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/860
288 .. _`#974`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/974
289 .. _`#1143`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1143
290 .. _`#1298`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1298
291 .. _`#1457`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1457
292 .. _`#1484`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1484
293 .. _`#1525`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1525
294 .. _`#1564`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1564
295 .. _`#1579`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1579
296 .. _`#1658`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1658
297 .. _`#1679`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1679
298 .. _`#1693`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1693
299 .. _`#1713`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1713
300 .. _`#1735`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1735
301 .. _`#1746`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1746
302 .. _`#1758`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1758
303 .. _`#1761`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1761
304 .. _`#1771`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1771
305 .. _`#1781`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1781
306 .. _`#1783`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1783
307 .. _`#1802`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1802
308 .. _`#1805`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1805
309 .. _`#1812`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1812
310 .. _`#1915`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1915
311 .. _`#1926`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1926
312 .. _`message to the tahoe-dev mailing list`:
313 https://tahoe-lafs.org/pipermail/tahoe-dev/2013-March/008096.html
316 Release 1.9.2 (2012-07-03)
317 ''''''''''''''''''''''''''
322 - Several regressions in support for reading (`#1636`_), writing/modifying
323 (`#1670`_, `#1749`_), verifying (`#1628`_) and repairing (`#1655`_, `#1669`_,
324 `#1676`_, `#1689`_) mutable files have been fixed.
325 - FTP can now list directories containing mutable files, although it
326 still does not support reading or writing mutable files. (`#680`_)
327 - The FTP frontend would previously show Jan 1 1970 for all timestamps;
328 now it shows the correct modification time of the directory entry.
330 - If a node is configured to report incidents to a log gatherer, but the
331 gatherer is offline when some incidents occur, it would previously not
332 "catch up" with those incidents as intended. (`#1725`_)
333 - OpenBSD 5 is now supported. (`#1584`_)
334 - The ``count-good-share-hosts`` field of file check results is now
335 computed correctly. (`#1115`_)
337 Configuration/Behavior Changes
338 ------------------------------
340 - The capability of the upload directory for the drop-upload frontend
341 is now specified in the file ``private/drop_upload_dircap`` under
342 the gateway's node directory, rather than in its ``tahoe.cfg``.
348 - Tahoe-LAFS can be built correctly from a git repository as well as
351 Compatibility and Dependencies
352 ------------------------------
354 - foolscap >= 0.6.3 is required, in order to make Tahoe-LAFS compatible
355 with Twisted >= 11.1.0. (`#1788`_)
356 - Versions 2.0.1 and 2.4 of PyCrypto are excluded. (`#1631`_, `#1574`_)
358 .. _`#680`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/680
359 .. _`#1115`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1115
360 .. _`#1574`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1574
361 .. _`#1584`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1584
362 .. _`#1593`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1593
363 .. _`#1628`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1628
364 .. _`#1631`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1631
365 .. _`#1636`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1636
366 .. _`#1655`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1655
367 .. _`#1669`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1669
368 .. _`#1670`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1670
369 .. _`#1676`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1676
370 .. _`#1688`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1688
371 .. _`#1689`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1689
372 .. _`#1725`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1725
373 .. _`#1749`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1749
374 .. _`#1788`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1788
377 Release 1.9.1 (2012-01-12)
378 ''''''''''''''''''''''''''
380 Security-related Bugfix
381 -----------------------
383 - Fix flaw that would allow servers to cause undetected corruption when
384 retrieving the contents of mutable files (both SDMF and MDMF). (`#1654`_)
386 .. _`#1654`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1654
389 Release 1.9.0 (2011-10-30)
390 ''''''''''''''''''''''''''
395 - The most significant new feature in this release is MDMF: "Medium-size
396 Distributed Mutable Files". Unlike standard SDMF files, these provide
397 efficient partial-access (reading and modifying small portions of the file
398 instead of the whole thing). MDMF is opt-in (it is not yet the default
399 format for mutable files), both to ensure compatibility with previous
400 versions, and because the algorithm does not yet meet memory-usage goals.
401 Enable it with ``--format=MDMF`` in the CLI (``tahoe put`` and ``tahoe
402 mkdir``), or the "format" radioboxes in the web interface. See
403 `<docs/specifications/mutable.rst>`__ for more details (`#393`_, `#1507`_)
404 - A "blacklist" feature allows blocking access to specific files through
405 a particular gateway. See the "Access Blacklist" section of
406 `<docs/configuration.rst>`__ for more details. (`#1425`_)
407 - A "drop-upload" feature has been added, which allows you to upload
408 files to a Tahoe-LAFS directory just by writing them to a local
409 directory. This feature is experimental and should not be relied on
410 to store the only copy of valuable data. It is currently available
411 only on Linux. See `<docs/frontends/drop-upload.rst>`__ for documentation.
413 - The timeline of immutable downloads can be viewed using a zoomable and
414 pannable JavaScript-based visualization. This is accessed using the
415 'timeline' link on the File Download Status page for the download, which
416 can be reached from the Recent Uploads and Downloads page.
418 Configuration/Behavior Changes
419 ------------------------------
421 - Prior to Tahoe-LAFS v1.3, the configuration of some node options could
422 be specified using individual config files rather than via ``tahoe.cfg``.
423 These files now cause an error if present. (`#1385`_)
424 - Storage servers now calculate their remaining space based on the filesystem
425 containing the ``storage/shares/`` directory. Previously they looked at the
426 filesystem containing the ``storage/`` directory. This allows
427 ``storage/shares/``, rather than ``storage/``, to be a mount point or a
428 symlink pointing to another filesystem. (`#1384`_)
429 - ``tahoe cp xyz MUTABLE`` will modify the existing mutable file instead of
430 creating a new one. (`#1304`_)
431 - The button for unlinking a file from its directory on a WUI directory
432 listing is now labelled "unlink" rather than "del". (`#1104`_)
437 - The security bugfix for the vulnerability allowing deletion of shares,
438 detailed in the news for v1.8.3 below, is also included in this
440 - Some cases of immutable upload, for example using the ``tahoe put`` and
441 ``tahoe cp`` commands or SFTP, did not appear in the history of Recent
442 Uploads and Downloads. (`#1079`_)
443 - The memory footprint of the verifier has been reduced by serializing
444 block fetches. (`#1395`_)
445 - Large immutable downloads are now a little faster than in v1.8.3 (about
446 5% on a fast network). (`#1268`_)
451 - The files related to Debian packaging have been removed from the Tahoe
452 source tree, since they are now maintained as part of the official
453 Debian packages. (`#1454`_)
454 - The unmaintained FUSE plugins were removed from the source tree. See
455 ``docs/frontends/FTP-and-SFTP.rst`` for how to mount a Tahoe filesystem on
456 Unix via sshfs. (`#1409`_)
457 - The Tahoe licenses now give explicit permission to combine Tahoe-LAFS
458 with code distributed under the following additional open-source licenses
459 (any version of each):
461 * Academic Free License
462 * Apple Public Source License
463 * BitTorrent Open Source License
464 * Lucent Public License
465 * Jabber Open Source License
466 * Common Development and Distribution License
467 * Microsoft Public License
468 * Microsoft Reciprocal License
469 * Sun Industry Standards Source License
470 * Open Software License
472 Compatibility and Dependencies
473 ------------------------------
475 - To resolve an incompatibility between Nevow and zope.interface (versions
476 3.6.3 and 3.6.4), Tahoe-LAFS now requires an earlier or later
477 version of zope.interface. (`#1435`_)
478 - The Twisted dependency has been raised to version 10.1 to ensure we no
479 longer require pywin32 on Windows, the new drop-upload feature has the
480 required support from Twisted on Linux, and that it is never necessary to
481 patch Twisted in order to use the FTP frontend. (`#1274`_, `#1429`_,
483 - An explicit dependency on pyOpenSSL has been added, replacing the indirect
484 dependency via the "secure_connections" option of foolscap. (`#1383`_)
489 - A ``man`` page has been added (`#1420`_). All other docs are in ReST
491 - The ``tahoe_files`` munin plugin reported an incorrect count of the number
492 of share files. (`#1391`_)
493 - Minor documentation updates: #627, #1104, #1225, #1297, #1342, #1404
494 - Other minor changes: #636, #1355, #1363, #1366, #1388, #1392, #1412, #1344,
495 #1347, #1359, #1389, #1441, #1442, #1446, #1474, #1503
497 .. _`#393`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/393
498 .. _`#1079`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1079
499 .. _`#1104`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1104
500 .. _`#1268`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1268
501 .. _`#1274`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1274
502 .. _`#1304`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1304
503 .. _`#1383`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1383
504 .. _`#1384`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1384
505 .. _`#1385`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1385
506 .. _`#1391`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1391
507 .. _`#1395`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1395
508 .. _`#1409`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1409
509 .. _`#1420`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1420
510 .. _`#1425`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1425
511 .. _`#1429`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1429
512 .. _`#1435`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1435
513 .. _`#1438`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1438
514 .. _`#1454`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1454
515 .. _`#1507`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1507
518 Release 1.8.3 (2011-09-13)
519 ''''''''''''''''''''''''''
521 Security-related Bugfix
522 -----------------------
524 - Fix flaw that would allow a person who knows a storage index of a file to
525 delete shares of that file. (`#1528`_)
526 - Remove corner cases in mutable file bounds management which could expose
527 extra lease info or old share data (from prior versions of the mutable
528 file) if someone with write authority to that mutable file exercised these
529 corner cases in a way that no actual Tahoe-LAFS client does. (Probably not
530 exploitable.) (`#1528`_)
532 .. _`#1528`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1528
535 Release 1.8.2 (2011-01-30)
536 ''''''''''''''''''''''''''
538 Compatibility and Dependencies
539 ------------------------------
541 - Tahoe is now compatible with Twisted-10.2 (released last month), as
542 well as with earlier versions. The previous Tahoe-1.8.1 release
543 failed to run against Twisted-10.2, raising an AttributeError on
544 StreamServerEndpointService (`#1286`_)
545 - Tahoe now depends upon the "mock" testing library, and the foolscap
546 dependency was raised to 0.6.1 . It no longer requires pywin32
547 (which was used only on windows). Future developers should note that
548 reactor.spawnProcess and derivatives may no longer be used inside
554 - the default reserved_space value for new storage nodes is 1 GB
556 - documentation is now in reStructuredText (.rst) format
557 - "tahoe cp" should now handle non-ASCII filenames
558 - the unmaintained Mac/Windows GUI applications have been removed
560 - tahoe processes should appear in top and ps as "tahoe", not
561 "python", on some unix platforms. (`#174`_)
562 - "tahoe debug trial" can be used to run the test suite (`#1296`_)
563 - the SFTP frontend now reports unknown sizes as "0" instead of "?",
564 to improve compatibility with clients like FileZilla (`#1337`_)
565 - "tahoe --version" should now report correct values in situations
566 where 1.8.1 might have been wrong (`#1287`_)
568 .. _`#1208`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1208
569 .. _`#1282`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1282
570 .. _`#1286`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1286
571 .. _`#1287`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1287
572 .. _`#1296`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1296
573 .. _`#1337`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1337
576 Release 1.8.1 (2010-10-28)
577 ''''''''''''''''''''''''''
579 Bugfixes and Improvements
580 -------------------------
582 - Allow the repairer to improve the health of a file by uploading some
583 shares, even if it cannot achieve the configured happiness
584 threshold. This fixes a regression introduced between v1.7.1 and
586 - Fix a memory leak in the ResponseCache which is used during mutable
587 file/directory operations. (`#1045`_)
588 - Fix a regression and add a performance improvement in the
589 downloader. This issue caused repair to fail in some special
591 - Fix a bug that caused 'tahoe cp' to fail for a grid-to-grid copy
592 involving a non-ASCII filename. (`#1224`_)
593 - Fix a rarely-encountered bug involving printing large strings to the
594 console on Windows. (`#1232`_)
595 - Perform ~ expansion in the --exclude-from filename argument to
596 'tahoe backup'. (`#1241`_)
597 - The CLI's 'tahoe mv' and 'tahoe ln' commands previously would try to
598 use an HTTP proxy if the HTTP_PROXY environment variable was set.
599 These now always connect directly to the WAPI, thus avoiding giving
600 caps to the HTTP proxy (and also avoiding failures in the case that
601 the proxy is failing or requires authentication). (`#1253`_)
602 - The CLI now correctly reports failure in the case that 'tahoe mv'
603 fails to unlink the file from its old location. (`#1255`_)
604 - 'tahoe start' now gives a more positive indication that the node has
606 - The arguments seen by 'ps' or other tools for node processes are now
607 more useful (in particular, they include the path of the 'tahoe'
608 script, rather than an obscure tool named 'twistd'). (`#174`_)
613 - The tahoe start/stop/restart and node creation commands no longer
614 accept the -m or --multiple option, for consistency between
615 platforms. (`#1262`_)
620 - We now host binary packages so that users on certain operating
621 systems can install without having a compiler.
622 <https://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-lafs-dep-eggs/README.html>
623 - Use a newer version of a dependency if needed, even if an older
624 version is installed. This would previously cause a VersionConflict
626 - Use a precompiled binary of a dependency if one with a sufficiently
627 high version number is available, instead of attempting to compile
628 the dependency from source, even if the source version has a higher
629 version number. (`#1233`_)
634 - All current documentation in .txt format has been converted to .rst
636 - Added docs/backdoors.rst declaring that we won't add backdoors to
637 Tahoe-LAFS, or add anything to facilitate government access to data.
640 .. _`#71`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/71
641 .. _`#174`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/174
642 .. _`#1212`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1212
643 .. _`#1045`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1045
644 .. _`#1190`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1190
645 .. _`#1216`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1216
646 .. _`#1223`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1223
647 .. _`#1224`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1224
648 .. _`#1225`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1225
649 .. _`#1232`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1232
650 .. _`#1233`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1233
651 .. _`#1241`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1241
652 .. _`#1253`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1253
653 .. _`#1255`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1255
654 .. _`#1262`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1262
657 Release 1.8.0 (2010-09-23)
658 ''''''''''''''''''''''''''
663 - A completely new downloader which improves performance and
664 robustness of immutable-file downloads. It uses the fastest K
665 servers to download the data in K-way parallel. It automatically
666 fails over to alternate servers if servers fail in mid-download. It
667 allows seeking to arbitrary locations in the file (the previous
668 downloader which would only read the entire file sequentially from
669 beginning to end). It minimizes unnecessary round trips and
670 unnecessary bytes transferred to improve performance. It sends
671 requests to fewer servers to reduce the load on servers (the
672 previous one would send a small request to every server for every
673 download) (`#287`_, `#288`_, `#448`_, `#798`_, `#800`_, `#990`_,
675 - Non-ASCII command-line arguments and non-ASCII outputs now work on
676 Windows. In addition, the command-line tool now works on 64-bit
679 Bugfixes and Improvements
680 -------------------------
682 - Document and clean up the command-line options for specifying the
683 node's base directory. (`#188`_, `#706`_, `#715`_, `#772`_,
685 - The default node directory for Windows is ".tahoe" in the user's
686 home directory, the same as on other platforms. (`#890`_)
687 - Fix a case in which full cap URIs could be logged. (`#685`_,
689 - Fix bug in WUI in Python 2.5 when the system clock is set back to
690 1969. Now you can use Tahoe-LAFS with Python 2.5 and set your system
691 clock to 1969 and still use the WUI. (`#1055`_)
692 - Many improvements in code organization, tests, logging,
693 documentation, and packaging. (`#983`_, `#1074`_, `#1108`_,
694 `#1127`_, `#1129`_, `#1131`_, `#1166`_, `#1175`_)
699 - on x86 and x86-64 platforms, pycryptopp >= 0.5.20
700 - pycrypto 2.2 is excluded due to a bug
702 .. _`#188`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/188
703 .. _`#288`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/288
704 .. _`#448`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/448
705 .. _`#685`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/685
706 .. _`#706`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/706
707 .. _`#715`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/715
708 .. _`#772`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/772
709 .. _`#798`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/798
710 .. _`#800`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/800
711 .. _`#890`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/890
712 .. _`#983`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/983
713 .. _`#990`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/990
714 .. _`#1055`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1055
715 .. _`#1074`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1074
716 .. _`#1108`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1108
717 .. _`#1155`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1155
718 .. _`#1170`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1170
719 .. _`#1191`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1191
720 .. _`#1127`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1127
721 .. _`#1129`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1129
722 .. _`#1131`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1131
723 .. _`#1166`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1166
724 .. _`#1175`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1175
726 Release 1.7.1 (2010-07-18)
727 ''''''''''''''''''''''''''
729 Bugfixes and Improvements
730 -------------------------
732 - Fix bug in which uploader could fail with AssertionFailure or report
733 that it had achieved servers-of-happiness when it hadn't. (`#1118`_)
734 - Fix bug in which servers could get into a state where they would
735 refuse to accept shares of a certain file (`#1117`_)
736 - Add init scripts for managing the gateway server on Debian/Ubuntu
738 - Fix bug where server version number was always 0 on the welcome page
740 - Add new command-line command "tahoe unlink" as a synonym for "tahoe
742 - The FTP frontend now encrypts its temporary files, protecting their
743 contents from an attacker who is able to read the disk. (`#1083`_)
744 - Fix IP address detection on FreeBSD 7, 8, and 9 (`#1098`_)
745 - Fix minor layout issue in the Web User Interface with Internet
747 - Fix rarely-encountered incompatibility between Twisted logging
748 utility and the new unicode support added in v1.7.0 (`#1099`_)
749 - Forward-compatibility improvements for non-ASCII caps (`#1051`_)
754 - Simplify and tidy-up directories, unicode support, test code
755 (`#923`_, `#967`_, `#1072`_)
757 .. _`#776`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/776
758 .. _`#923`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/923
759 .. _`#961`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/961
760 .. _`#967`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/967
761 .. _`#1051`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1051
762 .. _`#1067`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1067
763 .. _`#1072`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1072
764 .. _`#1083`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1083
765 .. _`#1097`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1097
766 .. _`#1098`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1098
767 .. _`#1099`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1099
768 .. _`#1117`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1117
769 .. _`#1118`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1118
772 Release 1.7.0 (2010-06-18)
773 ''''''''''''''''''''''''''
778 - SFTP support (`#1037`_)
779 Your Tahoe-LAFS gateway now acts like a full-fledged SFTP server. It
780 has been tested with sshfs to provide a virtual filesystem in Linux.
781 Many users have asked for this feature. We hope that it serves them
782 well! See the `FTP-and-SFTP.rst`_ document to get
784 - support for non-ASCII character encodings (`#534`_)
785 Tahoe-LAFS now correctly handles filenames containing non-ASCII
786 characters on all supported platforms:
788 - when reading files in from the local filesystem (such as when you
789 run "tahoe backup" to back up your local files to a Tahoe-LAFS
791 - when writing files out to the local filesystem (such as when you
792 run "tahoe cp -r" to recursively copy files out of a Tahoe-LAFS
794 - when displaying filenames to the terminal (such as when you run
795 "tahoe ls"), subject to limitations of the terminal and locale;
796 - when parsing command-line arguments, except on Windows.
798 - Servers of Happiness (`#778`_)
799 Tahoe-LAFS now measures during immutable file upload to see how well
800 distributed it is across multiple servers. It aborts the upload if
801 the pieces of the file are not sufficiently well-distributed.
802 This behavior is controlled by a configuration parameter called
803 "servers of happiness". With the default settings for its erasure
804 coding, Tahoe-LAFS generates 10 shares for each file, such that any
805 3 of those shares are sufficient to recover the file. The default
806 value of "servers of happiness" is 7, which means that Tahoe-LAFS
807 will guarantee that there are at least 7 servers holding some of the
808 shares, such that any 3 of those servers can completely recover your
809 file. The new upload code also distributes the shares better than the
810 previous version in some cases and takes better advantage of
811 pre-existing shares (when a file has already been previously
812 uploaded). See the `architecture.rst`_ document [3] for details.
814 Bugfixes and Improvements
815 -------------------------
817 - Premature abort of upload if some shares were already present and
818 some servers fail. (`#608`_)
819 - python ./setup.py install -- can't create or remove files in install
821 - Network failure => internal TypeError. (`#902`_)
822 - Install of Tahoe on CentOS 5.4. (`#933`_)
823 - CLI option --node-url now supports https url. (`#1028`_)
824 - HTML/CSS template files were not correctly installed under
826 - MetadataSetter does not enforce restriction on setting "tahoe"
828 - ImportError: No module named
829 setuptools_darcs.setuptools_darcs. (`#1054`_)
830 - Renamed Title in xhtml files. (`#1062`_)
831 - Increase Python version dependency to 2.4.4, to avoid a critical
832 CPython security bug. (`#1066`_)
833 - Typo correction for the munin plugin tahoe_storagespace. (`#968`_)
834 - Fix warnings found by pylint. (`#973`_)
835 - Changing format of some documentation files. (`#1027`_)
836 - the misc/ directory was tied up. (`#1068`_)
837 - The 'ctime' and 'mtime' metadata fields are no longer written except
838 by "tahoe backup". (`#924`_)
839 - Unicode filenames in Tahoe-LAFS directories are normalized so that
840 names that differ only in how accents are encoded are treated as the
842 - Various small improvements to documentation. (`#937`_, `#911`_,
848 - The 'tahoe debug consolidate' subcommand (for converting old
849 allmydata Windows client backups to a newer format) has been
855 - the Python version dependency is raised to 2.4.4 in some cases
856 (2.4.3 for Redhat-based Linux distributions, 2.4.2 for UCS-2 builds)
860 - mock (only required by unit tests)
862 .. _`#534`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/534
863 .. _`#608`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/608
864 .. _`#778`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/778
865 .. _`#803`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/803
866 .. _`#902`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/902
867 .. _`#911`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/911
868 .. _`#924`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/924
869 .. _`#937`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/937
870 .. _`#933`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/933
871 .. _`#968`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/968
872 .. _`#973`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/973
873 .. _`#1024`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1024
874 .. _`#1027`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1027
875 .. _`#1028`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1028
876 .. _`#1033`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1033
877 .. _`#1034`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1034
878 .. _`#1037`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1037
879 .. _`#1054`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1054
880 .. _`#1062`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1062
881 .. _`#1066`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1066
882 .. _`#1068`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1068
883 .. _`#1076`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1076
884 .. _`#1082`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1082
885 .. _architecture.rst: docs/architecture.rst
886 .. _FTP-and-SFTP.rst: docs/frontends/FTP-and-SFTP.rst
888 Release 1.6.1 (2010-02-27)
889 ''''''''''''''''''''''''''
894 - Correct handling of Small Immutable Directories
896 Immutable directories can now be deep-checked and listed in the web
897 UI in all cases. (In v1.6.0, some operations, such as deep-check, on
898 a directory graph that included very small immutable directories,
899 would result in an exception causing the whole operation to abort.)
902 Usability Improvements
903 ----------------------
905 - Improved user interface messages and error reporting. (`#681`_,
907 - The timeouts for operation handles have been greatly increased, so
908 that you can view the results of an operation up to 4 days after it
909 has completed. After viewing them for the first time, the results
910 are retained for a further day. (`#577`_)
912 Release 1.6.0 (2010-02-01)
913 ''''''''''''''''''''''''''
918 - Immutable Directories
920 Tahoe-LAFS can now create and handle immutable
921 directories. (`#607`_, `#833`_, `#931`_) These are read just like
922 normal directories, but are "deep-immutable", meaning that all their
923 children (and everything reachable from those children) must be
924 immutable objects (i.e. immutable or literal files, and other
925 immutable directories).
927 These directories must be created in a single webapi call that
928 provides all of the children at once. (Since they cannot be changed
929 after creation, the usual create/add/add sequence cannot be used.)
930 They have URIs that start with "URI:DIR2-CHK:" or "URI:DIR2-LIT:",
931 and are described on the human-facing web interface (aka the "WUI")
932 with a "DIR-IMM" abbreviation (as opposed to "DIR" for the usual
933 read-write directories and "DIR-RO" for read-only directories).
935 Tahoe-LAFS releases before 1.6.0 cannot read the contents of an
936 immutable directory. 1.5.0 will tolerate their presence in a
937 directory listing (and display it as "unknown"). 1.4.1 and earlier
938 cannot tolerate them: a DIR-IMM child in any directory will prevent
939 the listing of that directory.
941 Immutable directories are repairable, just like normal immutable
944 The webapi "POST t=mkdir-immutable" call is used to create immutable
945 directories. See `webapi.rst`_ for details.
947 - "tahoe backup" now creates immutable directories, backupdb has
950 The "tahoe backup" command has been enhanced to create immutable
951 directories (in previous releases, it created read-only mutable
952 directories) (`#828`_). This is significantly faster, since it does
953 not need to create an RSA keypair for each new directory. Also
954 "DIR-IMM" immutable directories are repairable, unlike "DIR-RO"
955 read-only mutable directories at present. (A future Tahoe-LAFS
956 release should also be able to repair DIR-RO.)
958 In addition, the backupdb (used by "tahoe backup" to remember what
959 it has already copied) has been enhanced to store information about
960 existing immutable directories. This allows it to re-use directories
961 that have moved but still contain identical contents, or that have
962 been deleted and later replaced. (The 1.5.0 "tahoe backup" command
963 could only re-use directories that were in the same place as they
964 were in the immediately previous backup.) With this change, the
965 backup process no longer needs to read the previous snapshot out of
966 the Tahoe-LAFS grid, reducing the network load
967 considerably. (`#606`_)
969 A "null backup" (in which nothing has changed since the previous
970 backup) will require only two Tahoe-side operations: one to add an
971 Archives/$TIMESTAMP entry, and a second to update the Latest/
972 link. On the local disk side, it will readdir() all your local
973 directories and stat() all your local files.
975 If you've been using "tahoe backup" for a while, you will notice
976 that your first use of it after upgrading to 1.6.0 may take a long
977 time: it must create proper immutable versions of all the old
978 read-only mutable directories. This process won't take as long as
979 the initial backup (where all the file contents had to be uploaded
980 too): it will require time proportional to the number and size of
981 your directories. After this initial pass, all subsequent passes
982 should take a tiny fraction of the time.
984 As noted above, Tahoe-LAFS versions earlier than 1.5.0 cannot list a
985 directory containing an immutable subdirectory. Tahoe-LAFS versions
986 earlier than 1.6.0 cannot read the contents of an immutable
989 The "tahoe backup" command has been improved to skip over unreadable
990 objects (like device files, named pipes, and files with permissions
991 that prevent the command from reading their contents), instead of
992 throwing an exception and terminating the backup process. It also
993 skips over symlinks, because these cannot be represented faithfully
994 in the Tahoe-side filesystem. A warning message will be emitted each
995 time something is skipped. (`#729`_, `#850`_, `#641`_)
997 - "create-node" command added, "create-client" now implies
1000 The basic idea behind Tahoe-LAFS's client+server and client-only
1001 processes is that you are creating a general-purpose Tahoe-LAFS
1002 "node" process, which has several components that can be
1003 activated. Storage service is one of these optional components, as
1004 is the Helper, FTP server, and SFTP server. Web gateway
1005 functionality is nominally on this list, but it is always active; a
1006 future release will make it optional. There are three special
1007 purpose servers that can't currently be run as a component in a
1008 node: introducer, key-generator, and stats-gatherer.
1010 So now "tahoe create-node" will create a Tahoe-LAFS node process,
1011 and after creation you can edit its tahoe.cfg to enable or disable
1012 the desired services. It is a more general-purpose replacement for
1013 "tahoe create-client". The default configuration has storage
1014 service enabled. For convenience, the "--no-storage" argument makes
1015 a tahoe.cfg file that disables storage service. (`#760`_)
1017 "tahoe create-client" has been changed to create a Tahoe-LAFS node
1018 without a storage service. It is equivalent to "tahoe create-node
1019 --no-storage". This helps to reduce the confusion surrounding the
1020 use of a command with "client" in its name to create a storage
1021 *server*. Use "tahoe create-client" to create a purely client-side
1022 node. If you want to offer storage to the grid, use "tahoe
1023 create-node" instead.
1025 In the future, other services will be added to the node, and they
1026 will be controlled through options in tahoe.cfg . The most important
1027 of these services may get additional --enable-XYZ or --disable-XYZ
1028 arguments to "tahoe create-node".
1030 - Performance Improvements
1032 Download of immutable files begins as soon as the downloader has
1033 located the K necessary shares (`#928`_, `#287`_). In both the
1034 previous and current releases, a downloader will first issue queries
1035 to all storage servers on the grid to locate shares before it begins
1036 downloading the shares. In previous releases of Tahoe-LAFS, download
1037 would not begin until all storage servers on the grid had replied to
1038 the query, at which point K shares would be chosen for download from
1039 among the shares that were located. In this release, download begins
1040 as soon as any K shares are located. This means that downloads start
1041 sooner, which is particularly important if there is a server on the
1042 grid that is extremely slow or even hung in such a way that it will
1043 never respond. In previous releases such a server would have a
1044 negative impact on all downloads from that grid. In this release,
1045 such a server will have no impact on downloads, as long as K shares
1046 can be found on other, quicker, servers. This also means that
1047 downloads now use the "best-alacrity" servers that they talk to, as
1048 measured by how quickly the servers reply to the initial query. This
1049 might cause downloads to go faster, especially on grids with
1050 heterogeneous servers or geographical dispersion.
1055 - The webapi acquired a new "t=mkdir-with-children" command, to create
1056 and populate a directory in a single call. This is significantly
1057 faster than using separate "t=mkdir" and "t=set-children" operations
1058 (it uses one gateway-to-grid roundtrip, instead of three or
1061 - The t=set-children (note the hyphen) operation is now documented in
1062 webapi.rst, and is the new preferred spelling of the
1063 old t=set_children (with an underscore). The underscore version
1064 remains for backwards compatibility. (`#381`_, `#927`_)
1066 - The tracebacks produced by errors in CLI tools should now be in
1067 plain text, instead of HTML (which is unreadable outside of a
1070 - The [storage]reserved_space configuration knob (which causes the
1071 storage server to refuse shares when available disk space drops
1072 below a threshold) should work on Windows now, not just
1075 - "tahoe cp" should now exit with status "1" if it cannot figure out a
1076 suitable target filename, such as when you copy from a bare
1079 - "tahoe get" no longer creates a zero-length file upon
1082 - "tahoe ls" can now list single files. (`#457`_)
1084 - "tahoe deep-check --repair" should tolerate repair failures now,
1085 instead of halting traversal. (`#874`_, `#786`_)
1087 - "tahoe create-alias" no longer corrupts the aliases file if it had
1088 previously been edited to have no trailing newline. (`#741`_)
1090 - Many small packaging improvements were made to facilitate the
1091 "tahoe-lafs" package being included in Ubuntu. Several mac/win32
1092 binary libraries were removed, some figleaf code-coverage files were
1093 removed, a bundled copy of darcsver-1.2.1 was removed, and
1094 additional licensing text was added.
1096 - Several DeprecationWarnings for python2.6 were silenced. (`#859`_)
1098 - The checker --add-lease option would sometimes fail for shares
1099 stored on old (Tahoe v1.2.0) servers. (`#875`_)
1101 - The documentation for installing on Windows (docs/quickstart.rst)
1102 has been improved. (`#773`_)
1104 For other changes not mentioned here, see
1105 <https://tahoe-lafs.org/trac/tahoe-lafs/query?milestone=1.6.0&keywords=!~news-done>.
1106 To include the tickets mentioned above, go to
1107 <https://tahoe-lafs.org/trac/tahoe-lafs/query?milestone=1.6.0>.
1109 .. _`#121`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/121
1110 .. _`#287`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/287
1111 .. _`#381`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/381
1112 .. _`#457`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/457
1113 .. _`#533`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/533
1114 .. _`#577`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/577
1115 .. _`#606`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/606
1116 .. _`#607`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/607
1117 .. _`#637`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/637
1118 .. _`#641`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/641
1119 .. _`#646`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/646
1120 .. _`#681`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/681
1121 .. _`#729`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/729
1122 .. _`#741`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/741
1123 .. _`#760`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/760
1124 .. _`#761`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/761
1125 .. _`#773`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/773
1126 .. _`#786`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/786
1127 .. _`#828`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/828
1128 .. _`#833`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/833
1129 .. _`#859`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/859
1130 .. _`#874`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/874
1131 .. _`#875`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/875
1132 .. _`#931`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/931
1133 .. _`#837`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/837
1134 .. _`#850`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/850
1135 .. _`#927`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/927
1136 .. _`#928`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/928
1137 .. _`#939`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/939
1138 .. _`#948`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/948
1139 .. _webapi.rst: docs/frontends/webapi.rst
1141 Release 1.5.0 (2009-08-01)
1142 ''''''''''''''''''''''''''
1147 - Uploads of immutable files now use pipelined writes, improving
1148 upload speed slightly (10%) over high-latency connections. (`#392`_)
1150 - Processing large directories has been sped up, by removing a O(N^2)
1151 algorithm from the dirnode decoding path and retaining unmodified
1152 encrypted entries. (`#750`_, `#752`_)
1154 - The human-facing web interface (aka the "WUI") received a
1155 significant CSS makeover by Kevin Reid, making it much prettier and
1156 easier to read. The WUI "check" and "deep-check" forms now include a
1157 "Renew Lease" checkbox, mirroring the CLI --add-lease option, so
1158 leases can be added or renewed from the web interface.
1160 - The CLI "tahoe mv" command now refuses to overwrite
1161 directories. (`#705`_)
1163 - The CLI "tahoe webopen" command, when run without arguments, will
1164 now bring up the "Welcome Page" (node status and mkdir/upload
1167 - The 3.5MB limit on mutable files was removed, so it should be
1168 possible to upload arbitrarily-sized mutable files. Note, however,
1169 that the data format and algorithm remains the same, so using
1170 mutable files still requires bandwidth, computation, and RAM in
1171 proportion to the size of the mutable file. (`#694`_)
1173 - This version of Tahoe-LAFS will tolerate directory entries that
1174 contain filecap formats which it does not recognize: files and
1175 directories from the future. This should improve the user
1176 experience (for 1.5.0 users) when we add new cap formats in the
1177 future. Previous versions would fail badly, preventing the user from
1178 seeing or editing anything else in those directories. These
1179 unrecognized objects can be renamed and deleted, but obviously not
1180 read or written. Also they cannot generally be copied. (`#683`_)
1185 - deep-check-and-repair now tolerates read-only directories, such as
1186 the ones produced by the "tahoe backup" CLI command. Read-only
1187 directories and mutable files are checked, but not
1188 repaired. Previous versions threw an exception when attempting the
1189 repair and failed to process the remaining contents. We cannot yet
1190 repair these read-only objects, but at least this version allows the
1191 rest of the check+repair to proceed. (`#625`_)
1193 - A bug in 1.4.1 which caused a server to be listed multiple times
1194 (and frequently broke all connections to that server) was
1197 - The plaintext-hashing code was removed from the Helper interface,
1198 removing the Helper's ability to mount a
1199 partial-information-guessing attack. (`#722`_)
1201 Platform/packaging changes
1202 --------------------------
1204 - Tahoe-LAFS now runs on NetBSD, OpenBSD, ArchLinux, and NixOS, and on
1205 an embedded system based on an ARM CPU running at 266 MHz.
1207 - Unit test timeouts have been raised to allow the tests to complete
1208 on extremely slow platforms like embedded ARM-based NAS boxes, which
1209 may take several hours to run the test suite. An ARM-specific
1210 data-corrupting bug in an older version of Crypto++ (5.5.2) was
1211 identified: ARM-users are encouraged to use recent
1212 Crypto++/pycryptopp which avoids this problem.
1214 - Tahoe-LAFS now requires a SQLite library, either the sqlite3 that
1215 comes built-in with python2.5/2.6, or the add-on pysqlite2 if you're
1216 using python2.4. In the previous release, this was only needed for
1217 the "tahoe backup" command: now it is mandatory.
1219 - Several minor documentation updates were made.
1221 - To help get Tahoe-LAFS into Linux distributions like Fedora and
1222 Debian, packaging improvements are being made in both Tahoe-LAFS and
1223 related libraries like pycryptopp and zfec.
1225 - The Crypto++ library included in the pycryptopp package has been
1226 upgraded to version 5.6.0 of Crypto++, which includes a more
1227 efficient implementation of SHA-256 in assembly for x86 or amd64
1234 - no python-2.4.0 or 2.4.1 (2.4.2 is good) (they contained a bug in base64.b32decode)
1235 - avoid python-2.6 on windows with mingw: compiler issues
1236 - python2.4 requires pysqlite2 (2.5,2.6 does not)
1240 .. _#392: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/392
1241 .. _#625: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/625
1242 .. _#653: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/653
1243 .. _#683: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/683
1244 .. _#694: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/694
1245 .. _#705: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/705
1246 .. _#722: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/722
1247 .. _#750: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/750
1248 .. _#752: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/752
1250 Release 1.4.1 (2009-04-13)
1251 ''''''''''''''''''''''''''
1256 - The big feature for this release is the implementation of garbage
1257 collection, allowing Tahoe storage servers to delete shares for old
1258 deleted files. When enabled, this uses a "mark and sweep" process:
1259 clients are responsible for updating the leases on their shares
1260 (generally by running "tahoe deep-check --add-lease"), and servers
1261 are allowed to delete any share which does not have an up-to-date
1262 lease. The process is described in detail in
1263 `garbage-collection.rst`_.
1265 The server must be configured to enable garbage-collection, by
1266 adding directives to the [storage] section that define an age limit
1267 for shares. The default configuration will not delete any shares.
1269 Both servers and clients should be upgraded to this release to make
1270 the garbage-collection as pleasant as possible. 1.2.0 servers have
1271 code to perform the update-lease operation but it suffers from a
1272 fatal bug, while 1.3.0 servers have update-lease but will return an
1273 exception for unknown storage indices, causing clients to emit an
1274 Incident for each exception, slowing the add-lease process down to a
1275 crawl. 1.1.0 servers did not have the add-lease operation at all.
1277 Security/Usability Problems Fixed
1278 ---------------------------------
1280 - A super-linear algorithm in the Merkle Tree code was fixed, which
1281 previously caused e.g. download of a 10GB file to take several hours
1282 before the first byte of plaintext could be produced. The new
1283 "alacrity" is about 2 minutes. A future release should reduce this
1284 to a few seconds by fixing ticket `#442`_.
1286 - The previous version permitted a small timing attack (due to our use
1287 of strcmp) against the write-enabler and lease-renewal/cancel
1288 secrets. An attacker who could measure response-time variations of
1289 approximatly 3ns against a very noisy background time of about 15ms
1290 might be able to guess these secrets. We do not believe this attack
1291 was actually feasible. This release closes the attack by first
1292 hashing the two strings to be compared with a random secret.
1297 - In most cases, HTML tracebacks will only be sent if an "Accept:
1298 text/html" header was provided with the HTTP request. This will
1299 generally cause browsers to get an HTMLized traceback but send
1300 regular text/plain tracebacks to non-browsers (like the CLI
1301 clients). More errors have been mapped to useful HTTP error codes.
1303 - The streaming webapi operations (deep-check and manifest) now have a
1304 way to indicate errors (an output line that starts with "ERROR"
1305 instead of being legal JSON). See `webapi.rst`_ for
1308 - The storage server now has its own status page (at /storage), linked
1309 from the Welcome page. This page shows progress and results of the
1310 two new share-crawlers: one which merely counts shares (to give an
1311 estimate of how many files/directories are being stored in the
1312 grid), the other examines leases and reports how much space would be
1313 freed if GC were enabled. The page also shows how much disk space is
1314 present, used, reserved, and available for the Tahoe server, and
1315 whether the server is currently running in "read-write" mode or
1318 - When a directory node cannot be read (perhaps because of insufficent
1319 shares), a minimal webapi page is created so that the "more-info"
1320 links (including a Check/Repair operation) will still be accessible.
1322 - A new "reliability" page was added, with the beginnings of work on a
1323 statistical loss model. You can tell this page how many servers you
1324 are using and their independent failure probabilities, and it will
1325 tell you the likelihood that an arbitrary file will survive each
1326 repair period. The "numpy" package must be installed to access this
1327 page. A partial paper, written by Shawn Willden, has been added to
1328 docs/proposed/lossmodel.lyx .
1333 - "tahoe check" and "tahoe deep-check" now accept an "--add-lease"
1334 argument, to update a lease on all shares. This is the "mark" side
1335 of garbage collection.
1337 - In many cases, CLI error messages have been improved: the ugly
1338 HTMLized traceback has been replaced by a normal python traceback.
1340 - "tahoe deep-check" and "tahoe manifest" now have better error
1341 reporting. "tahoe cp" is now non-verbose by default.
1343 - "tahoe backup" now accepts several "--exclude" arguments, to ignore
1344 certain files (like editor temporary files and version-control
1345 metadata) during backup.
1347 - On windows, the CLI now accepts local paths like "c:\dir\file.txt",
1348 which previously was interpreted as a Tahoe path using a "c:" alias.
1350 - The "tahoe restart" command now uses "--force" by default (meaning
1351 it will start a node even if it didn't look like there was one
1354 - The "tahoe debug consolidate" command was added. This takes a series
1355 of independent timestamped snapshot directories (such as those
1356 created by the allmydata.com windows backup program, or a series of
1357 "tahoe cp -r" commands) and creates new snapshots that used shared
1358 read-only directories whenever possible (like the output of "tahoe
1359 backup"). In the most common case (when the snapshots are fairly
1360 similar), the result will use significantly fewer directories than
1361 the original, allowing "deep-check" and similar tools to run much
1362 faster. In some cases, the speedup can be an order of magnitude or
1363 more. This tool is still somewhat experimental, and only needs to
1364 be run on large backups produced by something other than "tahoe
1365 backup", so it was placed under the "debug" category.
1367 - "tahoe cp -r --caps-only tahoe:dir localdir" is a diagnostic tool
1368 which, instead of copying the full contents of files into the local
1369 directory, merely copies their filecaps. This can be used to verify
1370 the results of a "consolidation" operation.
1375 - The codebase no longer rauses RuntimeError as a kind of
1376 assert(). Specific exception classes were created for each previous
1377 instance of RuntimeError.
1379 - Many unit tests were changed to use a non-network test harness,
1380 speeding them up considerably.
1382 - Deep-traversal operations (manifest and deep-check) now walk
1383 individual directories in alphabetical order. Occasional turn breaks
1384 are inserted to prevent a stack overflow when traversing directories
1385 with hundreds of entries.
1387 - The experimental SFTP server had its path-handling logic changed
1388 slightly, to accomodate more SFTP clients, although there are still
1391 .. _#442: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/442
1392 .. _#645: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/645
1393 .. _garbage-collection.rst: docs/garbage-collection.rst
1395 Release 1.3.0 (2009-02-13)
1396 ''''''''''''''''''''''''''
1398 Checker/Verifier/Repairer
1399 -------------------------
1401 - The primary focus of this release has been writing a checker /
1402 verifier / repairer for files and directories. "Checking" is the
1403 act of asking storage servers whether they have a share for the
1404 given file or directory: if there are not enough shares available,
1405 the file or directory will be unrecoverable. "Verifying" is the act
1406 of downloading and cryptographically asserting that the server's
1407 share is undamaged: it requires more work (bandwidth and CPU) than
1408 checking, but can catch problems that simple checking
1409 cannot. "Repair" is the act of replacing missing or damaged shares
1412 - This release includes a full checker, a partial verifier, and a
1413 partial repairer. The repairer is able to handle missing shares: new
1414 shares are generated and uploaded to make up for the missing
1415 ones. This is currently the best application of the repairer: to
1416 replace shares that were lost because of server departure or
1417 permanent drive failure.
1419 - The repairer in this release is somewhat able to handle corrupted
1420 shares. The limitations are:
1422 - Immutable verifier is incomplete: not all shares are used, and not
1423 all fields of those shares are verified. Therefore the immutable
1424 verifier has only a moderate chance of detecting corrupted shares.
1425 - The mutable verifier is mostly complete: all shares are examined,
1426 and most fields of the shares are validated.
1427 - The storage server protocol offers no way for the repairer to
1428 replace or delete immutable shares. If corruption is detected, the
1429 repairer will upload replacement shares to other servers, but the
1430 corrupted shares will be left in place.
1431 - read-only directories and read-only mutable files must be repaired
1432 by someone who holds the write-cap: the read-cap is
1433 insufficient. Moreover, the deep-check-and-repair operation will
1434 halt with an error if it attempts to repair one of these read-only
1436 - Some forms of corruption can cause both download and repair
1437 operations to fail. A future release will fix this, since download
1438 should be tolerant of any corruption as long as there are at least
1439 'k' valid shares, and repair should be able to fix any file that is
1442 - If the downloader, verifier, or repairer detects share corruption,
1443 the servers which provided the bad shares will be notified (via a
1444 file placed in the BASEDIR/storage/corruption-advisories directory)
1445 so their operators can manually delete the corrupted shares and
1446 investigate the problem. In addition, the "incident gatherer"
1447 mechanism will automatically report share corruption to an incident
1448 gatherer service, if one is configured. Note that corrupted shares
1449 indicate hardware failures, serious software bugs, or malice on the
1450 part of the storage server operator, so a corrupted share should be
1451 considered highly unusual.
1453 - By periodically checking/repairing all files and directories,
1454 objects in the Tahoe filesystem remain resistant to recoverability
1455 failures due to missing and/or broken servers.
1457 - This release includes a wapi mechanism to initiate checks on
1458 individual files and directories (with or without verification, and
1459 with or without automatic repair). A related mechanism is used to
1460 initiate a "deep-check" on a directory: recursively traversing the
1461 directory and its children, checking (and/or verifying/repairing)
1462 everything underneath. Both mechanisms can be run with an
1463 "output=JSON" argument, to obtain machine-readable check/repair
1464 status results. These results include a copy of the filesystem
1465 statistics from the "deep-stats" operation (including total number
1466 of files, size histogram, etc). If repair is possible, a "Repair"
1467 button will appear on the results page.
1469 - The client web interface now features some extra buttons to initiate
1470 check and deep-check operations. When these operations finish, they
1471 display a results page that summarizes any problems that were
1472 encountered. All long-running deep-traversal operations, including
1473 deep-check, use a start-and-poll mechanism, to avoid depending upon
1474 a single long-lived HTTP connection. `webapi.rst`_ has
1480 - The "tahoe backup" command is new in this release, which creates
1481 efficient versioned backups of a local directory. Given a local
1482 pathname and a target Tahoe directory, this will create a read-only
1483 snapshot of the local directory in $target/Archives/$timestamp. It
1484 will also create $target/Latest, which is a reference to the latest
1485 such snapshot. Each time you run "tahoe backup" with the same source
1486 and target, a new $timestamp snapshot will be added. These snapshots
1487 will share directories that have not changed since the last backup,
1488 to speed up the process and minimize storage requirements. In
1489 addition, a small database is used to keep track of which local
1490 files have been uploaded already, to avoid uploading them a second
1491 time. This drastically reduces the work needed to do a "null backup"
1492 (when nothing has changed locally), making "tahoe backup' suitable
1493 to run from a daily cronjob.
1495 Note that the "tahoe backup" CLI command must be used in conjunction
1496 with a 1.3.0-or-newer Tahoe client node; there was a bug in the
1497 1.2.0 webapi implementation that would prevent the last step (create
1498 $target/Latest) from working.
1503 - The 12GiB (approximate) immutable-file-size limitation is
1504 lifted. This release knows how to handle so-called "v2 immutable
1505 shares", which permit immutable files of up to about 18 EiB (about
1506 3*10^14). These v2 shares are created if the file to be uploaded is
1507 too large to fit into v1 shares. v1 shares are created if the file
1508 is small enough to fit into them, so that files created with
1509 tahoe-1.3.0 can still be read by earlier versions if they are not
1510 too large. Note that storage servers also had to be changed to
1511 support larger files, and this release is the first release in which
1512 they are able to do that. Clients will detect which servers are
1513 capable of supporting large files on upload and will not attempt to
1514 upload shares of a large file to a server which doesn't support it.
1519 - Tahoe now includes experimental FTP and SFTP servers. When
1520 configured with a suitable method to translate username+password
1521 into a root directory cap, it provides simple access to the virtual
1522 filesystem. Remember that FTP is completely unencrypted: passwords,
1523 filenames, and file contents are all sent over the wire in
1524 cleartext, so FTP should only be used on a local (127.0.0.1)
1525 connection. This feature is still in development: there are no unit
1526 tests yet, and behavior with respect to Unicode filenames is
1527 uncertain. Please see `FTP-and-SFTP.rst`_ for
1528 configuration details. (`#512`_, `#531`_)
1533 - This release adds the 'tahoe create-alias' command, which is a
1534 combination of 'tahoe mkdir' and 'tahoe add-alias'. This also allows
1535 you to start using a new tahoe directory without exposing its URI in
1536 the argv list, which is publicly visible (through the process table)
1537 on most unix systems. Thanks to Kevin Reid for bringing this issue
1540 - The single-argument form of "tahoe put" was changed to create an
1541 unlinked file. I.e. "tahoe put bar.txt" will take the contents of a
1542 local "bar.txt" file, upload them to the grid, and print the
1543 resulting read-cap; the file will not be attached to any
1544 directories. This seemed a bit more useful than the previous
1545 behavior (copy stdin, upload to the grid, attach the resulting file
1546 into your default tahoe: alias in a child named 'bar.txt').
1548 - "tahoe put" was also fixed to handle mutable files correctly: "tahoe
1549 put bar.txt URI:SSK:..." will read the contents of the local bar.txt
1550 and use them to replace the contents of the given mutable file.
1552 - The "tahoe webopen" command was modified to accept aliases. This
1553 means "tahoe webopen tahoe:" will cause your web browser to open to
1554 a "wui" page that gives access to the directory associated with the
1555 default "tahoe:" alias. It should also accept leading slashes, like
1556 "tahoe webopen tahoe:/stuff".
1558 - Many esoteric debugging commands were moved down into a "debug"
1561 - tahoe debug dump-cap
1562 - tahoe debug dump-share
1563 - tahoe debug find-shares
1564 - tahoe debug catalog-shares
1565 - tahoe debug corrupt-share
1567 The last command ("tahoe debug corrupt-share") flips a random bit
1568 of the given local sharefile. This is used to test the file
1569 verifying/repairing code, and obviously should not be used on user
1572 The cli might not correctly handle arguments which contain non-ascii
1573 characters in Tahoe v1.3 (although depending on your platform it
1574 might, especially if your platform can be configured to pass such
1575 characters on the command-line in utf-8 encoding). See
1576 https://tahoe-lafs.org/trac/tahoe-lafs/ticket/565 for details.
1581 - The "default webapi port", used when creating a new client node (and
1582 in the getting-started documentation), was changed from 8123 to
1583 3456, to reduce confusion when Tahoe accessed through a Firefox
1584 browser on which the "Torbutton" extension has been installed. Port
1585 8123 is occasionally used as a Tor control port, so Torbutton adds
1586 8123 to Firefox's list of "banned ports" to avoid CSRF attacks
1587 against Tor. Once 8123 is banned, it is difficult to diagnose why
1588 you can no longer reach a Tahoe node, so the Tahoe default was
1589 changed. Note that 3456 is reserved by IANA for the "vat" protocol,
1590 but there are argueably more Torbutton+Tahoe users than vat users
1591 these days. Note that this will only affect newly-created client
1592 nodes. Pre-existing client nodes, created by earlier versions of
1593 tahoe, may still be listening on 8123.
1595 - All deep-traversal operations (start-manifest, start-deep-size,
1596 start-deep-stats, start-deep-check) now use a start-and-poll
1597 approach, instead of using a single (fragile) long-running
1598 synchronous HTTP connection. All these "start-" operations use POST
1599 instead of GET. The old "GET manifest", "GET deep-size", and "POST
1600 deep-check" operations have been removed.
1602 - The new "POST start-manifest" operation, when it finally completes,
1603 results in a table of (path,cap), instead of the list of verifycaps
1604 produced by the old "GET manifest". The table is available in
1605 several formats: use output=html, output=text, or output=json to
1606 choose one. The JSON output also includes stats, and a list of
1607 verifycaps and storage-index strings. The "return_to=" and
1608 "when_done=" arguments have been removed from the t=check and
1609 deep-check operations.
1611 - The top-level status page (/status) now has a machine-readable form,
1612 via "/status/?t=json". This includes information about the
1613 currently-active uploads and downloads, which may be useful for
1614 frontends that wish to display progress information. There is no
1615 easy way to correlate the activities displayed here with recent wapi
1618 - Any files in BASEDIR/public_html/ (configurable) will be served in
1619 response to requests in the /static/ portion of the URL space. This
1620 will simplify the deployment of javascript-based frontends that can
1621 still access wapi calls by conforming to the (regrettable)
1622 "same-origin policy".
1624 - The welcome page now has a "Report Incident" button, which is tied
1625 into the "Incident Gatherer" machinery. If the node is attached to
1626 an incident gatherer (via log_gatherer.furl), then pushing this
1627 button will cause an Incident to be signalled: this means recent log
1628 events are aggregated and sent in a bundle to the gatherer. The user
1629 can push this button after something strange takes place (and they
1630 can provide a short message to go along with it), and the relevant
1631 data will be delivered to a centralized incident-gatherer for later
1632 processing by operations staff.
1634 - The "HEAD" method should now work correctly, in addition to the
1635 usual "GET", "PUT", and "POST" methods. "HEAD" is supposed to return
1636 exactly the same headers as "GET" would, but without any of the
1637 actual response body data. For mutable files, this now does a brief
1638 mapupdate (to figure out the size of the file that would be
1639 returned), without actually retrieving the file's contents.
1641 - The "GET" operation on files can now support the HTTP "Range:"
1642 header, allowing requests for partial content. This allows certain
1643 media players to correctly stream audio and movies out of a Tahoe
1644 grid. The current implementation uses a disk-based cache in
1645 BASEDIR/private/cache/download , which holds the plaintext of the
1646 files being downloaded. Future implementations might not use this
1647 cache. GET for immutable files now returns an ETag header.
1649 - Each file and directory now has a "Show More Info" web page, which
1650 contains much of the information that was crammed into the directory
1651 page before. This includes readonly URIs, storage index strings,
1652 object type, buttons to control checking/verifying/repairing, and
1653 deep-check/deep-stats buttons (for directories). For mutable files,
1654 the "replace contents" upload form has been moved here too. As a
1655 result, the directory page is now much simpler and cleaner, and
1656 several potentially-misleading links (like t=uri) are now gone.
1658 - Slashes are discouraged in Tahoe file/directory names, since they
1659 cause problems when accessing the filesystem through the
1660 wapi. However, there are a couple of accidental ways to generate
1661 such names. This release tries to make it easier to correct such
1662 mistakes by escaping slashes in several places, allowing slashes in
1663 the t=info and t=delete commands, and in the source (but not the
1664 target) of a t=rename command.
1669 - Tahoe's dependencies have been extended to require the
1670 "[secure_connections]" feature from Foolscap, which will cause
1671 pyOpenSSL to be required and/or installed. If OpenSSL and its
1672 development headers are already installed on your system, this can
1673 occur automatically. Tahoe now uses pollreactor (instead of the
1674 default selectreactor) to work around a bug between pyOpenSSL and
1675 the most recent release of Twisted (8.1.0). This bug only affects
1676 unit tests (hang during shutdown), and should not impact regular
1679 - The Tahoe source code tarballs now come in two different forms:
1680 regular and "sumo". The regular tarball contains just Tahoe, nothing
1681 else. When building from the regular tarball, the build process will
1682 download any unmet dependencies from the internet (starting with the
1683 index at PyPI) so it can build and install them. The "sumo" tarball
1684 contains copies of all the libraries that Tahoe requires (foolscap,
1685 twisted, zfec, etc), so using the "sumo" tarball should not require
1686 any internet access during the build process. This can be useful if
1687 you want to build Tahoe while on an airplane, a desert island, or
1688 other bandwidth-limited environments.
1690 - Similarly, tahoe-lafs.org now hosts a "tahoe-deps" tarball which
1691 contains the latest versions of all these dependencies. This
1693 https://tahoe-lafs.org/source/tahoe/deps/tahoe-deps.tar.gz, can be
1694 unpacked in the tahoe source tree (or in its parent directory), and
1695 the build process should satisfy its downloading needs from it
1696 instead of reaching out to PyPI. This can be useful if you want to
1697 build Tahoe from a darcs checkout while on that airplane or desert
1700 - Because of the previous two changes ("sumo" tarballs and the
1701 "tahoe-deps" bundle), most of the files have been removed from
1702 misc/dependencies/ . This brings the regular Tahoe tarball down to
1703 2MB (compressed), and the darcs checkout (without history) to about
1704 7.6MB. A full darcs checkout will still be fairly large (because of
1705 the historical patches which included the dependent libraries), but
1706 a 'lazy' one should now be small.
1708 - The default "make" target is now an alias for "setup.py build",
1709 which itself is an alias for "setup.py develop --prefix support",
1710 with some extra work before and after (see setup.cfg). Most of the
1711 complicated platform-dependent code in the Makefile was rewritten in
1712 Python and moved into setup.py, simplifying things considerably.
1714 - Likewise, the "make test" target now delegates most of its work to
1715 "setup.py test", which takes care of getting PYTHONPATH configured
1716 to access the tahoe code (and dependencies) that gets put in
1717 support/lib/ by the build_tahoe step. This should allow unit tests
1718 to be run even when trial (which is part of Twisted) wasn't already
1719 installed (in this case, trial gets installed to support/bin because
1720 Twisted is a dependency of Tahoe).
1722 - Tahoe is now compatible with the recently-released Python 2.6 ,
1723 although it is recommended to use Tahoe on Python 2.5, on which it
1724 has received more thorough testing and deployment.
1726 - Tahoe is now compatible with simplejson-2.0.x . The previous release
1727 assumed that simplejson.loads always returned unicode strings, which
1728 is no longer the case in 2.0.x .
1730 Grid Management Tools
1731 ---------------------
1733 - Several tools have been added or updated in the misc/ directory,
1734 mostly munin plugins that can be used to monitor a storage grid.
1736 - The misc/spacetime/ directory contains a "disk watcher" daemon
1737 (startable with 'tahoe start'), which can be configured with a set
1738 of HTTP URLs (pointing at the wapi '/statistics' page of a bunch of
1739 storage servers), and will periodically fetch
1740 disk-used/disk-available information from all the servers. It keeps
1741 this information in an Axiom database (a sqlite-based library
1742 available from divmod.org). The daemon computes time-averaged rates
1743 of disk usage, as well as a prediction of how much time is left
1744 before the grid is completely full.
1746 - The misc/munin/ directory contains a new set of munin plugins
1747 (tahoe_diskleft, tahoe_diskusage, tahoe_doomsday) which talk to the
1748 disk-watcher and provide graphs of its calculations.
1750 - To support the disk-watcher, the Tahoe statistics component
1751 (visible through the wapi at the /statistics/ URL) now includes
1752 disk-used and disk-available information. Both are derived through
1753 an equivalent of the unix 'df' command (i.e. they ask the kernel
1754 for the number of free blocks on the partition that encloses the
1755 BASEDIR/storage directory). In the future, the disk-available
1756 number will be further influenced by the local storage policy: if
1757 that policy says that the server should refuse new shares when less
1758 than 5GB is left on the partition, then "disk-available" will
1759 report zero even though the kernel sees 5GB remaining.
1761 - The 'tahoe_overhead' munin plugin interacts with an
1762 allmydata.com-specific server which reports the total of the
1763 'deep-size' reports for all active user accounts, compares this
1764 with the disk-watcher data, to report on overhead percentages. This
1765 provides information on how much space could be recovered once
1766 Tahoe implements some form of garbage collection.
1768 Configuration Changes: single INI-format tahoe.cfg file
1769 -------------------------------------------------------
1771 - The Tahoe node is now configured with a single INI-format file,
1772 named "tahoe.cfg", in the node's base directory. Most of the
1773 previous multiple-separate-files are still read for backwards
1774 compatibility (the embedded SSH debug server and the
1775 advertised_ip_addresses files are the exceptions), but new
1776 directives will only be added to tahoe.cfg . The "tahoe
1777 create-client" command will create a tahoe.cfg for you, with sample
1778 values commented out. (ticket `#518`_)
1780 - tahoe.cfg now has controls for the foolscap "keepalive" and
1781 "disconnect" timeouts (`#521`_).
1783 - tahoe.cfg now has controls for the encoding parameters:
1784 "shares.needed" and "shares.total" in the "[client]" section. The
1785 default parameters are still 3-of-10.
1787 - The inefficient storage 'sizelimit' control (which established an
1788 upper bound on the amount of space that a storage server is allowed
1789 to consume) has been replaced by a lightweight 'reserved_space'
1790 control (which establishes a lower bound on the amount of remaining
1791 space). The storage server will reject all writes that would cause
1792 the remaining disk space (as measured by a '/bin/df' equivalent) to
1793 drop below this value. The "[storage]reserved_space=" tahoe.cfg
1794 parameter controls this setting. (note that this only affects
1795 immutable shares: it is an outstanding bug that reserved_space does
1796 not prevent the allocation of new mutable shares, nor does it
1797 prevent the growth of existing mutable shares).
1802 - Clients now declare which versions of the protocols they
1803 support. This is part of a new backwards-compatibility system:
1804 https://tahoe-lafs.org/trac/tahoe-lafs/wiki/Versioning .
1806 - The version strings for human inspection (as displayed on the
1807 Welcome web page, and included in logs) now includes a platform
1808 identifer (frequently including a linux distribution name, processor
1811 - Several bugs have been fixed, including one that would cause an
1812 exception (in the logs) if a wapi download operation was cancelled
1813 (by closing the TCP connection, or pushing the "stop" button in a
1816 - Tahoe now uses Foolscap "Incidents", writing an "incident report"
1817 file to logs/incidents/ each time something weird occurs. These
1818 reports are available to an "incident gatherer" through the flogtool
1819 command. For more details, please see the Foolscap logging
1820 documentation. An incident-classifying plugin function is provided
1821 in misc/incident-gatherer/classify_tahoe.py .
1823 - If clients detect corruption in shares, they now automatically
1824 report it to the server holding that share, if it is new enough to
1825 accept the report. These reports are written to files in
1826 BASEDIR/storage/corruption-advisories .
1828 - The 'nickname' setting is now defined to be a UTF-8 -encoded string,
1829 allowing non-ascii nicknames.
1831 - The 'tahoe start' command will now accept a --syslog argument and
1832 pass it through to twistd, making it easier to launch non-Tahoe
1833 nodes (like the cpu-watcher) and have them log to syslogd instead of
1834 a local file. This is useful when running a Tahoe node out of a USB
1837 - The Mac GUI in src/allmydata/gui/ has been improved.
1839 .. _#512: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/512
1840 .. _#518: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/518
1841 .. _#521: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/521
1842 .. _#531: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/531
1844 Release 1.2.0 (2008-07-21)
1845 ''''''''''''''''''''''''''
1850 - This release makes the immutable-file "ciphertext hash tree"
1851 mandatory. Previous releases allowed the uploader to decide whether
1852 their file would have an integrity check on the ciphertext or not. A
1853 malicious uploader could use this to create a readcap that would
1854 download as one file or a different one, depending upon which shares
1855 the client fetched first, with no errors raised. There are other
1856 integrity checks on the shares themselves, preventing a storage
1857 server or other party from violating the integrity properties of the
1858 read-cap: this failure was only exploitable by the uploader who
1859 gives you a carefully constructed read-cap. If you download the file
1860 with Tahoe 1.2.0 or later, you will not be vulnerable to this
1863 This change does not introduce a compatibility issue, because all
1864 existing versions of Tahoe will emit the ciphertext hash tree in
1870 - Tahoe now requires Foolscap-0.2.9 . It also requires pycryptopp 0.5
1871 or newer, since earlier versions had a bug that interacted with
1872 specific compiler versions that could sometimes result in incorrect
1873 encryption behavior. Both packages are included in the Tahoe source
1874 tarball in misc/dependencies/ , and should be built automatically
1880 - Web API directory pages should now contain properly-slash-terminated
1881 links to other directories. They have also stopped using absolute
1882 links in forms and pages (which interfered with the use of a
1883 front-end load-balancing proxy).
1885 - The behavior of the "Check This File" button changed, in conjunction
1886 with larger internal changes to file checking/verification. The
1887 button triggers an immediate check as before, but the outcome is
1888 shown on its own page, and does not get stored anywhere. As a
1889 result, the web directory page no longer shows historical checker
1892 - A new "Deep-Check" button has been added, which allows a user to
1893 initiate a recursive check of the given directory and all files and
1894 directories reachable from it. This can cause quite a bit of work,
1895 and has no intermediate progress information or feedback about the
1896 process. In addition, the results of the deep-check are extremely
1897 limited. A later release will improve this behavior.
1899 - The web server's behavior with respect to non-ASCII (unicode)
1900 filenames in the "GET save=true" operation has been improved. To
1901 achieve maximum compatibility with variously buggy web browsers, the
1902 server does not try to figure out the character set of the inbound
1903 filename. It just echoes the same bytes back to the browser in the
1904 Content-Disposition header. This seems to make both IE7 and Firefox
1907 Checker/Verifier/Repairer
1908 -------------------------
1910 - Tahoe is slowly acquiring convenient tools to check up on file
1911 health, examine existing shares for errors, and repair files that
1912 are not fully healthy. This release adds a mutable
1913 checker/verifier/repairer, although testing is very limited, and
1914 there are no web interfaces to trigger repair yet. The "Check"
1915 button next to each file or directory on the wapi page will perform
1916 a file check, and the "deep check" button on each directory will
1917 recursively check all files and directories reachable from there
1918 (which may take a very long time).
1920 Future releases will improve access to this functionality.
1922 Operations/Packaging
1923 --------------------
1925 - A "check-grid" script has been added, along with a Makefile
1926 target. This is intended (with the help of a pre-configured node
1927 directory) to check upon the health of a Tahoe grid, uploading and
1928 downloading a few files. This can be used as a monitoring tool for a
1929 deployed grid, to be run periodically and to signal an error if it
1930 ever fails. It also helps with compatibility testing, to verify that
1931 the latest Tahoe code is still able to handle files created by an
1934 - The munin plugins from misc/munin/ are now copied into any generated
1935 debian packages, and are made executable (and uncompressed) so they
1936 can be symlinked directly from /etc/munin/plugins/ .
1938 - Ubuntu "Hardy" was added as a supported debian platform, with a
1939 Makefile target to produce hardy .deb packages. Some notes have been
1940 added to `debian.rst`_ about building Tahoe on a debian/ubuntu
1943 - Storage servers now measure operation rates and
1944 latency-per-operation, and provides results through the /statistics
1945 web page as well as the stats gatherer. Munin plugins have been
1951 - Tahoe nodes now use Foolscap "incident logging" to record unusual
1952 events to their NODEDIR/logs/incidents/ directory. These incident
1953 files can be examined by Foolscap logging tools, or delivered to an
1954 external log-gatherer for further analysis. Note that Tahoe now
1955 requires Foolscap-0.2.9, since 0.2.8 had a bug that complained about
1956 "OSError: File exists" when trying to create the incidents/
1957 directory for a second time.
1959 - If no servers are available when retrieving a mutable file (like a
1960 directory), the node now reports an error instead of hanging
1961 forever. Earlier releases would not only hang (causing the wapi
1962 directory listing to get stuck half-way through), but the internal
1963 dirnode serialization would cause all subsequent attempts to
1964 retrieve or modify the same directory to hang as well. `#463`_
1966 - A minor internal exception (reported in logs/twistd.log, in the
1967 "stopProducing" method) was fixed, which complained about
1968 "self._paused_at not defined" whenever a file download was stopped
1969 from the web browser end.
1971 .. _#463: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/463
1972 .. _#491: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/491
1973 .. _debian.rst: docs/debian.rst
1975 Release 1.1.0 (2008-06-11)
1976 ''''''''''''''''''''''''''
1978 CLI: new "alias" model
1979 ----------------------
1981 - The new CLI code uses an scp/rsync -like interface, in which
1982 directories in the Tahoe storage grid are referenced by a
1983 colon-suffixed alias. The new commands look like:
1985 - tahoe cp local.txt tahoe:virtual.txt
1986 - tahoe ls work:subdir
1988 - More functionality is available through the CLI: creating unlinked
1989 files and directories, recursive copy in or out of the storage grid,
1990 hardlinks, and retrieving the raw read- or write- caps through the
1991 'ls' command. Please read `CLI.rst`_ for complete details.
1993 wapi: new pages, new commands
1994 -----------------------------
1996 - Several new pages were added to the web API:
1998 - /helper_status : to describe what a Helper is doing
1999 - /statistics : reports node uptime, CPU usage, other stats
2000 - /file : for easy file-download URLs, see `#221`_
2001 - /cap == /uri : future compatibility
2003 - The localdir=/localfile= and t=download operations were
2004 removed. These required special configuration to enable anyways, but
2005 this feature was a security problem, and was mostly obviated by the
2006 new "cp -r" command.
2008 - Several new options to the GET command were added:
2010 - t=deep-size : add up the size of all immutable files reachable from the directory
2011 - t=deep-stats : return a JSON-encoded description of number of files, size distribution, total size, etc
2013 - POST is now preferred over PUT for most operations which cause
2016 - Most wapi calls now accept overwrite=, and default to overwrite=true
2018 - "POST /uri/DIRCAP/parent/child?t=mkdir" is now the preferred API to
2019 create multiple directories at once, rather than ...?t=mkdir-p .
2021 - PUT to a mutable file ("PUT /uri/MUTABLEFILECAP", "PUT
2022 /uri/DIRCAP/child") will modify the file in-place.
2024 - more munin graphs in misc/munin/
2027 - tahoe-rootdir-space
2028 - tahoe_estimate_files
2029 - mutable files published/retrieved
2038 - setuptools (now required at runtime)
2040 New Mutable-File Code
2041 ---------------------
2043 - The mutable-file handling code (mostly used for directories) has
2044 been completely rewritten. The new scheme has a better API (with a
2045 modify() method) and is less likely to lose data when several
2046 uncoordinated writers change a file at the same time.
2048 - In addition, a single Tahoe process will coordinate its own
2049 writes. If you make two concurrent directory-modifying wapi calls to
2050 a single tahoe node, it will internally make one of them wait for
2051 the other to complete. This prevents auto-collision (`#391`_).
2053 - The new mutable-file code also detects errors during publish
2054 better. Earlier releases might believe that a mutable file was
2055 published when in fact it failed.
2060 - The node now monitors its own CPU usage, as a percentage, measured
2061 every 60 seconds. 1/5/15 minute moving averages are available on the
2062 /statistics web page and via the stats-gathering interface.
2064 - Clients now accelerate reconnection to all servers after being
2065 offline (`#374`_). When a client is offline for a long time, it
2066 scales back reconnection attempts to approximately once per hour, so
2067 it may take a while to make the first attempt, but once any attempt
2068 succeeds, the other server connections will be retried immediately.
2070 - A new "offloaded KeyGenerator" facility can be configured, to move
2071 RSA key generation out from, say, a wapi node, into a separate
2072 process. RSA keys can take several seconds to create, and so a wapi
2073 node which is being used for directory creation will be unavailable
2074 for anything else during this time. The Key Generator process will
2075 pre-compute a small pool of keys, to speed things up further. This
2076 also takes better advantage of multi-core CPUs, or SMP hosts.
2078 - The node will only use a potentially-slow "du -s" command at startup
2079 (to measure how much space has been used) if the "sizelimit"
2080 parameter has been configured (to limit how much space is
2081 used). Large storage servers should turn off sizelimit until a later
2082 release improves the space-management code, since "du -s" on a
2083 terabyte filesystem can take hours.
2085 - The Introducer now allows new announcements to replace old ones, to
2086 avoid buildups of obsolete announcements.
2088 - Immutable files are limited to about 12GiB (when using the default
2089 3-of-10 encoding), because larger files would be corrupted by the
2090 four-byte share-size field on the storage servers (`#439`_). A later
2091 release will remove this limit. Earlier releases would allow >12GiB
2092 uploads, but the resulting file would be unretrievable.
2094 - The docs/ directory has been rearranged, with old docs put in
2095 docs/historical/ and not-yet-implemented ones in docs/proposed/ .
2097 - The Mac OS-X FUSE plugin has a significant bug fix: earlier versions
2098 would corrupt writes that used seek() instead of writing the file in
2099 linear order. The rsync tool is known to perform writes in this
2100 order. This has been fixed.
2102 .. _#221: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/221
2103 .. _#374: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/374
2104 .. _#391: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/391
2105 .. _#439: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/439
2106 .. _CLI.rst: docs/CLI.rst