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