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