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