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