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