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