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