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