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