2 ==================================
3 User-Visible Changes in Tahoe-LAFS
4 ==================================
6 Release 1.10 (2013-??-??)
11 - The Welcome page has been redesigned. This is a preview of the design style
12 that is likely to be used in other parts of the WUI in future Tahoe-LAFS
13 versions. (`#1713`_, `#1457`_, `#1735`_)
14 - A new, more extensible Introducer protocol has been added, to act as the
15 basis for future improvements such as accounting. Compatibility with older
16 nodes is not affected. When server, introducer, and client are all
17 upgraded, the welcome page will show node IDs that start with "v0-" instead
18 of the old tubid. (`#466`_)
19 - The web-API has a new move operation that supports directly moving files
20 between directories. (`#1579`_)
25 - The ``introducer.furl`` for new Introducers is now unguessable. In previous
26 releases, this FURL used a predictable swissnum, allowing a network
27 eavesdropper (who observes any node connecting to the Introducer) to access
28 the Introducer themselves, and thus use servers or offer storage service to
29 clients (i.e. "join the grid"). In the new code, the only way to join a
30 grid is to be told the introducer.furl by someone who already knew it. Note
31 that pre-existing introducers are not changed: to take advantage of this
32 fix for an existing grid, you must create a new introducer and distribute
33 the new ``introducer.furl`` to all of your users. (`#1802`_)
34 - Both ``introducer.furl`` and ``helper.furl`` are now censored from the
35 Welcome page, to prevent users of your gateway from learning enough to
36 create gateway nodes of their own. (`#860`_)
37 - If an immutable file failed to download, e.g. due to a connection problem,
38 subsequent attempts to download the same file could also fail. (`#1679`_)
39 - The SFTP frontend works with recent versions of Twisted, rather than
40 giving errors or warnings about use of ``IFinishableConsumer``. (`#1926`_,
42 - Failure handling in the SFTP frontend has been improved. (`#1525`_)
43 - Checking a LIT file using ``tahoe check`` no longer results in an
45 - Filenames in WUI directory pages are now displayed correctly when they
46 contain characters that require HTML escaping. (`#1143`_)
47 - Non-ASCII node nicknames no longer cause WUI errors. (`#1298`_)
48 - Error messages containing tracebacks may be slightly more readable.
50 - ``tahoe cp --verbose`` counts the files being processed correctly.
52 - Exceptions no longer trigger an unhelpful crash reporter on Ubuntu 12.04
53 ("Precise") or later. (`#1746`_)
54 - Improve error message when CLI tools cannot connect to a gateway. (`#974`_)
56 Performance Improvements
57 ''''''''''''''''''''''''
59 - Allow web clients to cache immutable directory pages. (`#443`_)
64 - docs/helper.rst has been brought up to date. (`#1915`_)
65 - docs/convergence_secret.rst was added to document the adminstration of
66 convergence secrets. (`#1761`_)
71 - The flogtool utility, used to read logs, can now be accessed as
72 ``tahoe debug flogtool`` even when foolscap is not installed system-wide.
74 - The provisioning/reliability pages were removed from the main client's web
75 interface, and moved into a standalone web-based tool in
76 misc/operations_helpers/provisioning. Use the ``run.py`` script to access
79 Compatibility and Dependencies
80 ''''''''''''''''''''''''''''''
82 - Python >= 2.6, except Python 3 (`#1658`_)
83 - Twisted >= 11.0.0 (`#1771`_)
85 - pycryptopp >= 0.6.0 (for ed25519)
87 Precautions when Upgrading
88 ''''''''''''''''''''''''''
90 - When upgrading a grid from a recent version of trunk, follow the
91 precautions from this `message to the tahoe-dev mailing list`_, to ensure
92 that announcements to the Introducer are recognized after the upgrade.
93 This is not necessary when upgrading from a previous release.
95 .. _`#443`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/443
96 .. _`#466`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/466
97 .. _`#1143`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1143
98 .. _`#1298`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1298
99 .. _`#1457`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1457
100 .. _`#1484`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1484
101 .. _`#1525`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1525
102 .. _`#1564`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1564
103 .. _`#1579`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1579
104 .. _`#1658`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1658
105 .. _`#1679`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1679
106 .. _`#1693`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1693
107 .. _`#1713`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1713
108 .. _`#1735`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1735
109 .. _`#1746`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1746
110 .. _`#1758`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1758
111 .. _`#1761`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1761
112 .. _`#1771`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1771
113 .. _`#1783`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1783
114 .. _`#1805`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1805
115 .. _`#1915`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1915
116 .. _`#1926`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1926
117 .. _`message to the tahoe-dev mailing list`:
118 https://tahoe-lafs.org/pipermail/tahoe-dev/2013-March/008096.html
120 Release 1.9.2 (2012-07-03)
121 --------------------------
126 - Several regressions in support for reading (`#1636`_), writing/modifying
127 (`#1670`_, `#1749`_), verifying (`#1628`_) and repairing (`#1655`_, `#1669`_,
128 `#1676`_, `#1689`_) mutable files have been fixed.
129 - FTP can now list directories containing mutable files, although it
130 still does not support reading or writing mutable files. (`#680`_)
131 - The FTP frontend would previously show Jan 1 1970 for all timestamps;
132 now it shows the correct modification time of the directory entry.
134 - If a node is configured to report incidents to a log gatherer, but the
135 gatherer is offline when some incidents occur, it would previously not
136 "catch up" with those incidents as intended. (`#1725`_)
137 - OpenBSD 5 is now supported. (`#1584`_)
138 - The ``count-good-share-hosts`` field of file check results is now
139 computed correctly. (`#1115`_)
141 Configuration/Behavior Changes
142 ''''''''''''''''''''''''''''''
144 - The capability of the upload directory for the drop-upload frontend
145 is now specified in the file ``private/drop_upload_dircap`` under
146 the gateway's node directory, rather than in its ``tahoe.cfg``.
152 - Tahoe-LAFS can be built correctly from a git repository as well as
155 Compatibility and Dependencies
156 ''''''''''''''''''''''''''''''
158 - foolscap >= 0.6.3 is required, in order to make Tahoe-LAFS compatible
159 with Twisted >= 11.1.0. (`#1788`_)
160 - Versions 2.0.1 and 2.4 of PyCrypto are excluded. (`#1631`_, `#1574`_)
162 .. _`#680`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/680
163 .. _`#1115`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1115
164 .. _`#1574`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1574
165 .. _`#1584`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1584
166 .. _`#1593`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1593
167 .. _`#1628`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1628
168 .. _`#1631`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1631
169 .. _`#1636`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1636
170 .. _`#1655`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1655
171 .. _`#1669`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1669
172 .. _`#1670`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1670
173 .. _`#1676`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1676
174 .. _`#1688`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1688
175 .. _`#1689`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1689
176 .. _`#1725`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1725
177 .. _`#1749`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1749
178 .. _`#1788`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1788
181 Release 1.9.1 (2012-01-12)
182 --------------------------
184 Security-related Bugfix
185 '''''''''''''''''''''''
187 - Fix flaw that would allow servers to cause undetected corruption when
188 retrieving the contents of mutable files (both SDMF and MDMF). (`#1654`_)
190 .. _`#1654`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1654
193 Release 1.9.0 (2011-10-30)
194 --------------------------
199 - The most significant new feature in this release is MDMF: "Medium-size
200 Distributed Mutable Files". Unlike standard SDMF files, these provide
201 efficient partial-access (reading and modifying small portions of the file
202 instead of the whole thing). MDMF is opt-in (it is not yet the default
203 format for mutable files), both to ensure compatibility with previous
204 versions, and because the algorithm does not yet meet memory-usage goals.
205 Enable it with ``--format=MDMF`` in the CLI (``tahoe put`` and ``tahoe
206 mkdir``), or the "format" radioboxes in the web interface. See
207 `<docs/specifications/mutable.rst>`__ for more details (`#393`_, `#1507`_)
208 - A "blacklist" feature allows blocking access to specific files through
209 a particular gateway. See the "Access Blacklist" section of
210 `<docs/configuration.rst>`__ for more details. (`#1425`_)
211 - A "drop-upload" feature has been added, which allows you to upload
212 files to a Tahoe-LAFS directory just by writing them to a local
213 directory. This feature is experimental and should not be relied on
214 to store the only copy of valuable data. It is currently available
215 only on Linux. See `<docs/frontends/drop-upload.rst>`__ for documentation.
217 - The timeline of immutable downloads can be viewed using a zoomable and
218 pannable JavaScript-based visualization. This is accessed using the
219 'timeline' link on the File Download Status page for the download, which
220 can be reached from the Recent Uploads and Downloads page.
222 Configuration/Behavior Changes
223 ''''''''''''''''''''''''''''''
225 - Prior to Tahoe-LAFS v1.3, the configuration of some node options could
226 be specified using individual config files rather than via ``tahoe.cfg``.
227 These files now cause an error if present. (`#1385`_)
228 - Storage servers now calculate their remaining space based on the filesystem
229 containing the ``storage/shares/`` directory. Previously they looked at the
230 filesystem containing the ``storage/`` directory. This allows
231 ``storage/shares/``, rather than ``storage/``, to be a mount point or a
232 symlink pointing to another filesystem. (`#1384`_)
233 - ``tahoe cp xyz MUTABLE`` will modify the existing mutable file instead of
234 creating a new one. (`#1304`_)
235 - The button for unlinking a file from its directory on a WUI directory
236 listing is now labelled "unlink" rather than "del". (`#1104`_)
241 - The security bugfix for the vulnerability allowing deletion of shares,
242 detailed in the news for v1.8.3 below, is also included in this
244 - Some cases of immutable upload, for example using the ``tahoe put`` and
245 ``tahoe cp`` commands or SFTP, did not appear in the history of Recent
246 Uploads and Downloads. (`#1079`_)
247 - The memory footprint of the verifier has been reduced by serializing
248 block fetches. (`#1395`_)
249 - Large immutable downloads are now a little faster than in v1.8.3 (about
250 5% on a fast network). (`#1268`_)
255 - The files related to Debian packaging have been removed from the Tahoe
256 source tree, since they are now maintained as part of the official
257 Debian packages. (`#1454`_)
258 - The unmaintained FUSE plugins were removed from the source tree. See
259 ``docs/frontends/FTP-and-SFTP.rst`` for how to mount a Tahoe filesystem on
260 Unix via sshfs. (`#1409`_)
261 - The Tahoe licenses now give explicit permission to combine Tahoe-LAFS
262 with code distributed under the following additional open-source licenses
263 (any version of each):
265 * Academic Free License
266 * Apple Public Source License
267 * BitTorrent Open Source License
268 * Lucent Public License
269 * Jabber Open Source License
270 * Common Development and Distribution License
271 * Microsoft Public License
272 * Microsoft Reciprocal License
273 * Sun Industry Standards Source License
274 * Open Software License
276 Compatibility and Dependencies
277 ''''''''''''''''''''''''''''''
279 - To resolve an incompatibility between Nevow and zope.interface (versions
280 3.6.3 and 3.6.4), Tahoe-LAFS now requires an earlier or later
281 version of zope.interface. (`#1435`_)
282 - The Twisted dependency has been raised to version 10.1 to ensure we no
283 longer require pywin32 on Windows, the new drop-upload feature has the
284 required support from Twisted on Linux, and that it is never necessary to
285 patch Twisted in order to use the FTP frontend. (`#1274`_, `#1429`_,
287 - An explicit dependency on pyOpenSSL has been added, replacing the indirect
288 dependency via the "secure_connections" option of foolscap. (`#1383`_)
293 - A ``man`` page has been added (`#1420`_). All other docs are in ReST
295 - The ``tahoe_files`` munin plugin reported an incorrect count of the number
296 of share files. (`#1391`_)
297 - Minor documentation updates: #627, #1104, #1225, #1297, #1342, #1404
298 - Other minor changes: #636, #1355, #1363, #1366, #1388, #1392, #1412, #1344,
299 #1347, #1359, #1389, #1441, #1442, #1446, #1474, #1503
301 .. _`#393`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/393
302 .. _`#1079`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1079
303 .. _`#1104`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1104
304 .. _`#1268`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1268
305 .. _`#1274`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1274
306 .. _`#1304`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1304
307 .. _`#1383`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1383
308 .. _`#1384`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1384
309 .. _`#1385`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1385
310 .. _`#1391`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1391
311 .. _`#1395`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1395
312 .. _`#1409`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1409
313 .. _`#1420`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1420
314 .. _`#1425`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1425
315 .. _`#1429`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1429
316 .. _`#1435`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1435
317 .. _`#1438`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1438
318 .. _`#1454`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1454
319 .. _`#1507`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1507
322 Release 1.8.3 (2011-09-13)
323 --------------------------
325 Security-related Bugfix
326 '''''''''''''''''''''''
328 - Fix flaw that would allow a person who knows a storage index of a file to
329 delete shares of that file. (`#1528`_)
330 - Remove corner cases in mutable file bounds management which could expose
331 extra lease info or old share data (from prior versions of the mutable
332 file) if someone with write authority to that mutable file exercised these
333 corner cases in a way that no actual Tahoe-LAFS client does. (Probably not
334 exploitable.) (`#1528`_)
336 .. _`#1528`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1528
339 Release 1.8.2 (2011-01-30)
340 --------------------------
342 Compatibility and Dependencies
343 ''''''''''''''''''''''''''''''
345 - Tahoe is now compatible with Twisted-10.2 (released last month), as
346 well as with earlier versions. The previous Tahoe-1.8.1 release
347 failed to run against Twisted-10.2, raising an AttributeError on
348 StreamServerEndpointService (`#1286`_)
349 - Tahoe now depends upon the "mock" testing library, and the foolscap
350 dependency was raised to 0.6.1 . It no longer requires pywin32
351 (which was used only on windows). Future developers should note that
352 reactor.spawnProcess and derivatives may no longer be used inside
358 - the default reserved_space value for new storage nodes is 1 GB
360 - documentation is now in reStructuredText (.rst) format
361 - "tahoe cp" should now handle non-ASCII filenames
362 - the unmaintained Mac/Windows GUI applications have been removed
364 - tahoe processes should appear in top and ps as "tahoe", not
365 "python", on some unix platforms. (`#174`_)
366 - "tahoe debug trial" can be used to run the test suite (`#1296`_)
367 - the SFTP frontend now reports unknown sizes as "0" instead of "?",
368 to improve compatibility with clients like FileZilla (`#1337`_)
369 - "tahoe --version" should now report correct values in situations
370 where 1.8.1 might have been wrong (`#1287`_)
372 .. _`#1208`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1208
373 .. _`#1282`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1282
374 .. _`#1286`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1286
375 .. _`#1287`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1287
376 .. _`#1296`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1296
377 .. _`#1337`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1337
380 Release 1.8.1 (2010-10-28)
381 --------------------------
383 Bugfixes and Improvements
384 '''''''''''''''''''''''''
386 - Allow the repairer to improve the health of a file by uploading some
387 shares, even if it cannot achieve the configured happiness
388 threshold. This fixes a regression introduced between v1.7.1 and
390 - Fix a memory leak in the ResponseCache which is used during mutable
391 file/directory operations. (`#1045`_)
392 - Fix a regression and add a performance improvement in the
393 downloader. This issue caused repair to fail in some special
395 - Fix a bug that caused 'tahoe cp' to fail for a grid-to-grid copy
396 involving a non-ASCII filename. (`#1224`_)
397 - Fix a rarely-encountered bug involving printing large strings to the
398 console on Windows. (`#1232`_)
399 - Perform ~ expansion in the --exclude-from filename argument to
400 'tahoe backup'. (`#1241`_)
401 - The CLI's 'tahoe mv' and 'tahoe ln' commands previously would try to
402 use an HTTP proxy if the HTTP_PROXY environment variable was set.
403 These now always connect directly to the WAPI, thus avoiding giving
404 caps to the HTTP proxy (and also avoiding failures in the case that
405 the proxy is failing or requires authentication). (`#1253`_)
406 - The CLI now correctly reports failure in the case that 'tahoe mv'
407 fails to unlink the file from its old location. (`#1255`_)
408 - 'tahoe start' now gives a more positive indication that the node has
410 - The arguments seen by 'ps' or other tools for node processes are now
411 more useful (in particular, they include the path of the 'tahoe'
412 script, rather than an obscure tool named 'twistd'). (`#174`_)
417 - The tahoe start/stop/restart and node creation commands no longer
418 accept the -m or --multiple option, for consistency between
419 platforms. (`#1262`_)
424 - We now host binary packages so that users on certain operating
425 systems can install without having a compiler.
426 <https://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-lafs-dep-eggs/README.html>
427 - Use a newer version of a dependency if needed, even if an older
428 version is installed. This would previously cause a VersionConflict
430 - Use a precompiled binary of a dependency if one with a sufficiently
431 high version number is available, instead of attempting to compile
432 the dependency from source, even if the source version has a higher
433 version number. (`#1233`_)
438 - All current documentation in .txt format has been converted to .rst
440 - Added docs/backdoors.rst declaring that we won't add backdoors to
441 Tahoe-LAFS, or add anything to facilitate government access to data.
444 .. _`#71`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/71
445 .. _`#174`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/174
446 .. _`#1212`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1212
447 .. _`#1045`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1045
448 .. _`#1190`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1190
449 .. _`#1216`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1216
450 .. _`#1223`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1223
451 .. _`#1224`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1224
452 .. _`#1225`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1225
453 .. _`#1232`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1232
454 .. _`#1233`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1233
455 .. _`#1241`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1241
456 .. _`#1253`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1253
457 .. _`#1255`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1255
458 .. _`#1262`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1262
461 Release 1.8.0 (2010-09-23)
462 --------------------------
467 - A completely new downloader which improves performance and
468 robustness of immutable-file downloads. It uses the fastest K
469 servers to download the data in K-way parallel. It automatically
470 fails over to alternate servers if servers fail in mid-download. It
471 allows seeking to arbitrary locations in the file (the previous
472 downloader which would only read the entire file sequentially from
473 beginning to end). It minimizes unnecessary round trips and
474 unnecessary bytes transferred to improve performance. It sends
475 requests to fewer servers to reduce the load on servers (the
476 previous one would send a small request to every server for every
477 download) (`#287`_, `#288`_, `#448`_, `#798`_, `#800`_, `#990`_,
479 - Non-ASCII command-line arguments and non-ASCII outputs now work on
480 Windows. In addition, the command-line tool now works on 64-bit
483 Bugfixes and Improvements
484 '''''''''''''''''''''''''
486 - Document and clean up the command-line options for specifying the
487 node's base directory. (`#188`_, `#706`_, `#715`_, `#772`_,
489 - The default node directory for Windows is ".tahoe" in the user's
490 home directory, the same as on other platforms. (`#890`_)
491 - Fix a case in which full cap URIs could be logged. (`#685`_,
493 - Fix bug in WUI in Python 2.5 when the system clock is set back to
494 1969. Now you can use Tahoe-LAFS with Python 2.5 and set your system
495 clock to 1969 and still use the WUI. (`#1055`_)
496 - Many improvements in code organization, tests, logging,
497 documentation, and packaging. (`#983`_, `#1074`_, `#1108`_,
498 `#1127`_, `#1129`_, `#1131`_, `#1166`_, `#1175`_)
503 - on x86 and x86-64 platforms, pycryptopp >= 0.5.20
504 - pycrypto 2.2 is excluded due to a bug
506 .. _`#188`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/188
507 .. _`#288`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/288
508 .. _`#448`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/448
509 .. _`#685`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/685
510 .. _`#706`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/706
511 .. _`#715`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/715
512 .. _`#772`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/772
513 .. _`#798`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/798
514 .. _`#800`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/800
515 .. _`#890`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/890
516 .. _`#983`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/983
517 .. _`#990`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/990
518 .. _`#1055`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1055
519 .. _`#1074`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1074
520 .. _`#1108`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1108
521 .. _`#1155`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1155
522 .. _`#1170`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1170
523 .. _`#1191`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1191
524 .. _`#1127`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1127
525 .. _`#1129`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1129
526 .. _`#1131`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1131
527 .. _`#1166`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1166
528 .. _`#1175`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1175
530 Release 1.7.1 (2010-07-18)
531 --------------------------
533 Bugfixes and Improvements
534 '''''''''''''''''''''''''
536 - Fix bug in which uploader could fail with AssertionFailure or report
537 that it had achieved servers-of-happiness when it hadn't. (`#1118`_)
538 - Fix bug in which servers could get into a state where they would
539 refuse to accept shares of a certain file (`#1117`_)
540 - Add init scripts for managing the gateway server on Debian/Ubuntu
542 - Fix bug where server version number was always 0 on the welcome page
544 - Add new command-line command "tahoe unlink" as a synonym for "tahoe
546 - The FTP frontend now encrypts its temporary files, protecting their
547 contents from an attacker who is able to read the disk. (`#1083`_)
548 - Fix IP address detection on FreeBSD 7, 8, and 9 (`#1098`_)
549 - Fix minor layout issue in the Web User Interface with Internet
551 - Fix rarely-encountered incompatibility between Twisted logging
552 utility and the new unicode support added in v1.7.0 (`#1099`_)
553 - Forward-compatibility improvements for non-ASCII caps (`#1051`_)
558 - Simplify and tidy-up directories, unicode support, test code
559 (`#923`_, `#967`_, `#1072`_)
561 .. _`#776`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/776
562 .. _`#923`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/923
563 .. _`#961`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/961
564 .. _`#967`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/967
565 .. _`#1051`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1051
566 .. _`#1067`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1067
567 .. _`#1072`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1072
568 .. _`#1083`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1083
569 .. _`#1097`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1097
570 .. _`#1098`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1098
571 .. _`#1099`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1099
572 .. _`#1117`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1117
573 .. _`#1118`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1118
576 Release 1.7.0 (2010-06-18)
577 --------------------------
582 - SFTP support (`#1037`_)
583 Your Tahoe-LAFS gateway now acts like a full-fledged SFTP server. It
584 has been tested with sshfs to provide a virtual filesystem in Linux.
585 Many users have asked for this feature. We hope that it serves them
586 well! See the `FTP-and-SFTP.rst`_ document to get
588 - support for non-ASCII character encodings (`#534`_)
589 Tahoe-LAFS now correctly handles filenames containing non-ASCII
590 characters on all supported platforms:
592 - when reading files in from the local filesystem (such as when you
593 run "tahoe backup" to back up your local files to a Tahoe-LAFS
595 - when writing files out to the local filesystem (such as when you
596 run "tahoe cp -r" to recursively copy files out of a Tahoe-LAFS
598 - when displaying filenames to the terminal (such as when you run
599 "tahoe ls"), subject to limitations of the terminal and locale;
600 - when parsing command-line arguments, except on Windows.
602 - Servers of Happiness (`#778`_)
603 Tahoe-LAFS now measures during immutable file upload to see how well
604 distributed it is across multiple servers. It aborts the upload if
605 the pieces of the file are not sufficiently well-distributed.
606 This behavior is controlled by a configuration parameter called
607 "servers of happiness". With the default settings for its erasure
608 coding, Tahoe-LAFS generates 10 shares for each file, such that any
609 3 of those shares are sufficient to recover the file. The default
610 value of "servers of happiness" is 7, which means that Tahoe-LAFS
611 will guarantee that there are at least 7 servers holding some of the
612 shares, such that any 3 of those servers can completely recover your
613 file. The new upload code also distributes the shares better than the
614 previous version in some cases and takes better advantage of
615 pre-existing shares (when a file has already been previously
616 uploaded). See the `architecture.rst`_ document [3] for details.
618 Bugfixes and Improvements
619 '''''''''''''''''''''''''
621 - Premature abort of upload if some shares were already present and
622 some servers fail. (`#608`_)
623 - python ./setup.py install -- can't create or remove files in install
625 - Network failure => internal TypeError. (`#902`_)
626 - Install of Tahoe on CentOS 5.4. (`#933`_)
627 - CLI option --node-url now supports https url. (`#1028`_)
628 - HTML/CSS template files were not correctly installed under
630 - MetadataSetter does not enforce restriction on setting "tahoe"
632 - ImportError: No module named
633 setuptools_darcs.setuptools_darcs. (`#1054`_)
634 - Renamed Title in xhtml files. (`#1062`_)
635 - Increase Python version dependency to 2.4.4, to avoid a critical
636 CPython security bug. (`#1066`_)
637 - Typo correction for the munin plugin tahoe_storagespace. (`#968`_)
638 - Fix warnings found by pylint. (`#973`_)
639 - Changing format of some documentation files. (`#1027`_)
640 - the misc/ directory was tied up. (`#1068`_)
641 - The 'ctime' and 'mtime' metadata fields are no longer written except
642 by "tahoe backup". (`#924`_)
643 - Unicode filenames in Tahoe-LAFS directories are normalized so that
644 names that differ only in how accents are encoded are treated as the
646 - Various small improvements to documentation. (`#937`_, `#911`_,
652 - The 'tahoe debug consolidate' subcommand (for converting old
653 allmydata Windows client backups to a newer format) has been
659 - the Python version dependency is raised to 2.4.4 in some cases
660 (2.4.3 for Redhat-based Linux distributions, 2.4.2 for UCS-2 builds)
664 - mock (only required by unit tests)
666 .. _`#534`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/534
667 .. _`#608`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/608
668 .. _`#778`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/778
669 .. _`#803`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/803
670 .. _`#902`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/902
671 .. _`#911`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/911
672 .. _`#924`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/924
673 .. _`#937`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/937
674 .. _`#933`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/933
675 .. _`#968`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/968
676 .. _`#973`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/973
677 .. _`#1024`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1024
678 .. _`#1027`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1027
679 .. _`#1028`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1028
680 .. _`#1033`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1033
681 .. _`#1034`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1034
682 .. _`#1037`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1037
683 .. _`#1054`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1054
684 .. _`#1062`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1062
685 .. _`#1066`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1066
686 .. _`#1068`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1068
687 .. _`#1076`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1076
688 .. _`#1082`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1082
689 .. _architecture.rst: docs/architecture.rst
690 .. _FTP-and-SFTP.rst: docs/frontends/FTP-and-SFTP.rst
692 Release 1.6.1 (2010-02-27)
693 --------------------------
698 - Correct handling of Small Immutable Directories
700 Immutable directories can now be deep-checked and listed in the web
701 UI in all cases. (In v1.6.0, some operations, such as deep-check, on
702 a directory graph that included very small immutable directories,
703 would result in an exception causing the whole operation to abort.)
706 Usability Improvements
707 ''''''''''''''''''''''
709 - Improved user interface messages and error reporting. (`#681`_,
711 - The timeouts for operation handles have been greatly increased, so
712 that you can view the results of an operation up to 4 days after it
713 has completed. After viewing them for the first time, the results
714 are retained for a further day. (`#577`_)
716 Release 1.6.0 (2010-02-01)
717 --------------------------
722 - Immutable Directories
724 Tahoe-LAFS can now create and handle immutable
725 directories. (`#607`_, `#833`_, `#931`_) These are read just like
726 normal directories, but are "deep-immutable", meaning that all their
727 children (and everything reachable from those children) must be
728 immutable objects (i.e. immutable or literal files, and other
729 immutable directories).
731 These directories must be created in a single webapi call that
732 provides all of the children at once. (Since they cannot be changed
733 after creation, the usual create/add/add sequence cannot be used.)
734 They have URIs that start with "URI:DIR2-CHK:" or "URI:DIR2-LIT:",
735 and are described on the human-facing web interface (aka the "WUI")
736 with a "DIR-IMM" abbreviation (as opposed to "DIR" for the usual
737 read-write directories and "DIR-RO" for read-only directories).
739 Tahoe-LAFS releases before 1.6.0 cannot read the contents of an
740 immutable directory. 1.5.0 will tolerate their presence in a
741 directory listing (and display it as "unknown"). 1.4.1 and earlier
742 cannot tolerate them: a DIR-IMM child in any directory will prevent
743 the listing of that directory.
745 Immutable directories are repairable, just like normal immutable
748 The webapi "POST t=mkdir-immutable" call is used to create immutable
749 directories. See `webapi.rst`_ for details.
751 - "tahoe backup" now creates immutable directories, backupdb has
754 The "tahoe backup" command has been enhanced to create immutable
755 directories (in previous releases, it created read-only mutable
756 directories) (`#828`_). This is significantly faster, since it does
757 not need to create an RSA keypair for each new directory. Also
758 "DIR-IMM" immutable directories are repairable, unlike "DIR-RO"
759 read-only mutable directories at present. (A future Tahoe-LAFS
760 release should also be able to repair DIR-RO.)
762 In addition, the backupdb (used by "tahoe backup" to remember what
763 it has already copied) has been enhanced to store information about
764 existing immutable directories. This allows it to re-use directories
765 that have moved but still contain identical contents, or that have
766 been deleted and later replaced. (The 1.5.0 "tahoe backup" command
767 could only re-use directories that were in the same place as they
768 were in the immediately previous backup.) With this change, the
769 backup process no longer needs to read the previous snapshot out of
770 the Tahoe-LAFS grid, reducing the network load
771 considerably. (`#606`_)
773 A "null backup" (in which nothing has changed since the previous
774 backup) will require only two Tahoe-side operations: one to add an
775 Archives/$TIMESTAMP entry, and a second to update the Latest/
776 link. On the local disk side, it will readdir() all your local
777 directories and stat() all your local files.
779 If you've been using "tahoe backup" for a while, you will notice
780 that your first use of it after upgrading to 1.6.0 may take a long
781 time: it must create proper immutable versions of all the old
782 read-only mutable directories. This process won't take as long as
783 the initial backup (where all the file contents had to be uploaded
784 too): it will require time proportional to the number and size of
785 your directories. After this initial pass, all subsequent passes
786 should take a tiny fraction of the time.
788 As noted above, Tahoe-LAFS versions earlier than 1.5.0 cannot list a
789 directory containing an immutable subdirectory. Tahoe-LAFS versions
790 earlier than 1.6.0 cannot read the contents of an immutable
793 The "tahoe backup" command has been improved to skip over unreadable
794 objects (like device files, named pipes, and files with permissions
795 that prevent the command from reading their contents), instead of
796 throwing an exception and terminating the backup process. It also
797 skips over symlinks, because these cannot be represented faithfully
798 in the Tahoe-side filesystem. A warning message will be emitted each
799 time something is skipped. (`#729`_, `#850`_, `#641`_)
801 - "create-node" command added, "create-client" now implies
804 The basic idea behind Tahoe-LAFS's client+server and client-only
805 processes is that you are creating a general-purpose Tahoe-LAFS
806 "node" process, which has several components that can be
807 activated. Storage service is one of these optional components, as
808 is the Helper, FTP server, and SFTP server. Web gateway
809 functionality is nominally on this list, but it is always active; a
810 future release will make it optional. There are three special
811 purpose servers that can't currently be run as a component in a
812 node: introducer, key-generator, and stats-gatherer.
814 So now "tahoe create-node" will create a Tahoe-LAFS node process,
815 and after creation you can edit its tahoe.cfg to enable or disable
816 the desired services. It is a more general-purpose replacement for
817 "tahoe create-client". The default configuration has storage
818 service enabled. For convenience, the "--no-storage" argument makes
819 a tahoe.cfg file that disables storage service. (`#760`_)
821 "tahoe create-client" has been changed to create a Tahoe-LAFS node
822 without a storage service. It is equivalent to "tahoe create-node
823 --no-storage". This helps to reduce the confusion surrounding the
824 use of a command with "client" in its name to create a storage
825 *server*. Use "tahoe create-client" to create a purely client-side
826 node. If you want to offer storage to the grid, use "tahoe
827 create-node" instead.
829 In the future, other services will be added to the node, and they
830 will be controlled through options in tahoe.cfg . The most important
831 of these services may get additional --enable-XYZ or --disable-XYZ
832 arguments to "tahoe create-node".
834 - Performance Improvements
836 Download of immutable files begins as soon as the downloader has
837 located the K necessary shares (`#928`_, `#287`_). In both the
838 previous and current releases, a downloader will first issue queries
839 to all storage servers on the grid to locate shares before it begins
840 downloading the shares. In previous releases of Tahoe-LAFS, download
841 would not begin until all storage servers on the grid had replied to
842 the query, at which point K shares would be chosen for download from
843 among the shares that were located. In this release, download begins
844 as soon as any K shares are located. This means that downloads start
845 sooner, which is particularly important if there is a server on the
846 grid that is extremely slow or even hung in such a way that it will
847 never respond. In previous releases such a server would have a
848 negative impact on all downloads from that grid. In this release,
849 such a server will have no impact on downloads, as long as K shares
850 can be found on other, quicker, servers. This also means that
851 downloads now use the "best-alacrity" servers that they talk to, as
852 measured by how quickly the servers reply to the initial query. This
853 might cause downloads to go faster, especially on grids with
854 heterogeneous servers or geographical dispersion.
859 - The webapi acquired a new "t=mkdir-with-children" command, to create
860 and populate a directory in a single call. This is significantly
861 faster than using separate "t=mkdir" and "t=set-children" operations
862 (it uses one gateway-to-grid roundtrip, instead of three or
865 - The t=set-children (note the hyphen) operation is now documented in
866 webapi.rst, and is the new preferred spelling of the
867 old t=set_children (with an underscore). The underscore version
868 remains for backwards compatibility. (`#381`_, `#927`_)
870 - The tracebacks produced by errors in CLI tools should now be in
871 plain text, instead of HTML (which is unreadable outside of a
874 - The [storage]reserved_space configuration knob (which causes the
875 storage server to refuse shares when available disk space drops
876 below a threshold) should work on Windows now, not just
879 - "tahoe cp" should now exit with status "1" if it cannot figure out a
880 suitable target filename, such as when you copy from a bare
883 - "tahoe get" no longer creates a zero-length file upon
886 - "tahoe ls" can now list single files. (`#457`_)
888 - "tahoe deep-check --repair" should tolerate repair failures now,
889 instead of halting traversal. (`#874`_, `#786`_)
891 - "tahoe create-alias" no longer corrupts the aliases file if it had
892 previously been edited to have no trailing newline. (`#741`_)
894 - Many small packaging improvements were made to facilitate the
895 "tahoe-lafs" package being included in Ubuntu. Several mac/win32
896 binary libraries were removed, some figleaf code-coverage files were
897 removed, a bundled copy of darcsver-1.2.1 was removed, and
898 additional licensing text was added.
900 - Several DeprecationWarnings for python2.6 were silenced. (`#859`_)
902 - The checker --add-lease option would sometimes fail for shares
903 stored on old (Tahoe v1.2.0) servers. (`#875`_)
905 - The documentation for installing on Windows (docs/quickstart.rst)
906 has been improved. (`#773`_)
908 For other changes not mentioned here, see
909 <https://tahoe-lafs.org/trac/tahoe-lafs/query?milestone=1.6.0&keywords=!~news-done>.
910 To include the tickets mentioned above, go to
911 <https://tahoe-lafs.org/trac/tahoe-lafs/query?milestone=1.6.0>.
913 .. _`#121`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/121
914 .. _`#287`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/287
915 .. _`#381`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/381
916 .. _`#457`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/457
917 .. _`#533`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/533
918 .. _`#577`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/577
919 .. _`#606`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/606
920 .. _`#607`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/607
921 .. _`#637`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/637
922 .. _`#641`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/641
923 .. _`#646`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/646
924 .. _`#681`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/681
925 .. _`#729`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/729
926 .. _`#741`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/741
927 .. _`#760`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/760
928 .. _`#761`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/761
929 .. _`#773`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/773
930 .. _`#786`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/786
931 .. _`#828`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/828
932 .. _`#833`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/833
933 .. _`#859`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/859
934 .. _`#874`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/874
935 .. _`#875`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/875
936 .. _`#931`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/931
937 .. _`#837`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/837
938 .. _`#850`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/850
939 .. _`#927`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/927
940 .. _`#928`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/928
941 .. _`#939`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/939
942 .. _`#948`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/948
943 .. _webapi.rst: docs/frontends/webapi.rst
945 Release 1.5.0 (2009-08-01)
946 --------------------------
951 - Uploads of immutable files now use pipelined writes, improving
952 upload speed slightly (10%) over high-latency connections. (`#392`_)
954 - Processing large directories has been sped up, by removing a O(N^2)
955 algorithm from the dirnode decoding path and retaining unmodified
956 encrypted entries. (`#750`_, `#752`_)
958 - The human-facing web interface (aka the "WUI") received a
959 significant CSS makeover by Kevin Reid, making it much prettier and
960 easier to read. The WUI "check" and "deep-check" forms now include a
961 "Renew Lease" checkbox, mirroring the CLI --add-lease option, so
962 leases can be added or renewed from the web interface.
964 - The CLI "tahoe mv" command now refuses to overwrite
965 directories. (`#705`_)
967 - The CLI "tahoe webopen" command, when run without arguments, will
968 now bring up the "Welcome Page" (node status and mkdir/upload
971 - The 3.5MB limit on mutable files was removed, so it should be
972 possible to upload arbitrarily-sized mutable files. Note, however,
973 that the data format and algorithm remains the same, so using
974 mutable files still requires bandwidth, computation, and RAM in
975 proportion to the size of the mutable file. (`#694`_)
977 - This version of Tahoe-LAFS will tolerate directory entries that
978 contain filecap formats which it does not recognize: files and
979 directories from the future. This should improve the user
980 experience (for 1.5.0 users) when we add new cap formats in the
981 future. Previous versions would fail badly, preventing the user from
982 seeing or editing anything else in those directories. These
983 unrecognized objects can be renamed and deleted, but obviously not
984 read or written. Also they cannot generally be copied. (`#683`_)
989 - deep-check-and-repair now tolerates read-only directories, such as
990 the ones produced by the "tahoe backup" CLI command. Read-only
991 directories and mutable files are checked, but not
992 repaired. Previous versions threw an exception when attempting the
993 repair and failed to process the remaining contents. We cannot yet
994 repair these read-only objects, but at least this version allows the
995 rest of the check+repair to proceed. (`#625`_)
997 - A bug in 1.4.1 which caused a server to be listed multiple times
998 (and frequently broke all connections to that server) was
1001 - The plaintext-hashing code was removed from the Helper interface,
1002 removing the Helper's ability to mount a
1003 partial-information-guessing attack. (`#722`_)
1005 Platform/packaging changes
1006 ''''''''''''''''''''''''''
1008 - Tahoe-LAFS now runs on NetBSD, OpenBSD, ArchLinux, and NixOS, and on
1009 an embedded system based on an ARM CPU running at 266 MHz.
1011 - Unit test timeouts have been raised to allow the tests to complete
1012 on extremely slow platforms like embedded ARM-based NAS boxes, which
1013 may take several hours to run the test suite. An ARM-specific
1014 data-corrupting bug in an older version of Crypto++ (5.5.2) was
1015 identified: ARM-users are encouraged to use recent
1016 Crypto++/pycryptopp which avoids this problem.
1018 - Tahoe-LAFS now requires a SQLite library, either the sqlite3 that
1019 comes built-in with python2.5/2.6, or the add-on pysqlite2 if you're
1020 using python2.4. In the previous release, this was only needed for
1021 the "tahoe backup" command: now it is mandatory.
1023 - Several minor documentation updates were made.
1025 - To help get Tahoe-LAFS into Linux distributions like Fedora and
1026 Debian, packaging improvements are being made in both Tahoe-LAFS and
1027 related libraries like pycryptopp and zfec.
1029 - The Crypto++ library included in the pycryptopp package has been
1030 upgraded to version 5.6.0 of Crypto++, which includes a more
1031 efficient implementation of SHA-256 in assembly for x86 or amd64
1038 - no python-2.4.0 or 2.4.1 (2.4.2 is good) (they contained a bug in base64.b32decode)
1039 - avoid python-2.6 on windows with mingw: compiler issues
1040 - python2.4 requires pysqlite2 (2.5,2.6 does not)
1044 .. _#392: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/392
1045 .. _#625: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/625
1046 .. _#653: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/653
1047 .. _#683: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/683
1048 .. _#694: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/694
1049 .. _#705: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/705
1050 .. _#722: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/722
1051 .. _#750: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/750
1052 .. _#752: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/752
1054 Release 1.4.1 (2009-04-13)
1055 --------------------------
1060 - The big feature for this release is the implementation of garbage
1061 collection, allowing Tahoe storage servers to delete shares for old
1062 deleted files. When enabled, this uses a "mark and sweep" process:
1063 clients are responsible for updating the leases on their shares
1064 (generally by running "tahoe deep-check --add-lease"), and servers
1065 are allowed to delete any share which does not have an up-to-date
1066 lease. The process is described in detail in
1067 `garbage-collection.rst`_.
1069 The server must be configured to enable garbage-collection, by
1070 adding directives to the [storage] section that define an age limit
1071 for shares. The default configuration will not delete any shares.
1073 Both servers and clients should be upgraded to this release to make
1074 the garbage-collection as pleasant as possible. 1.2.0 servers have
1075 code to perform the update-lease operation but it suffers from a
1076 fatal bug, while 1.3.0 servers have update-lease but will return an
1077 exception for unknown storage indices, causing clients to emit an
1078 Incident for each exception, slowing the add-lease process down to a
1079 crawl. 1.1.0 servers did not have the add-lease operation at all.
1081 Security/Usability Problems Fixed
1082 '''''''''''''''''''''''''''''''''
1084 - A super-linear algorithm in the Merkle Tree code was fixed, which
1085 previously caused e.g. download of a 10GB file to take several hours
1086 before the first byte of plaintext could be produced. The new
1087 "alacrity" is about 2 minutes. A future release should reduce this
1088 to a few seconds by fixing ticket `#442`_.
1090 - The previous version permitted a small timing attack (due to our use
1091 of strcmp) against the write-enabler and lease-renewal/cancel
1092 secrets. An attacker who could measure response-time variations of
1093 approximatly 3ns against a very noisy background time of about 15ms
1094 might be able to guess these secrets. We do not believe this attack
1095 was actually feasible. This release closes the attack by first
1096 hashing the two strings to be compared with a random secret.
1101 - In most cases, HTML tracebacks will only be sent if an "Accept:
1102 text/html" header was provided with the HTTP request. This will
1103 generally cause browsers to get an HTMLized traceback but send
1104 regular text/plain tracebacks to non-browsers (like the CLI
1105 clients). More errors have been mapped to useful HTTP error codes.
1107 - The streaming webapi operations (deep-check and manifest) now have a
1108 way to indicate errors (an output line that starts with "ERROR"
1109 instead of being legal JSON). See `webapi.rst`_ for
1112 - The storage server now has its own status page (at /storage), linked
1113 from the Welcome page. This page shows progress and results of the
1114 two new share-crawlers: one which merely counts shares (to give an
1115 estimate of how many files/directories are being stored in the
1116 grid), the other examines leases and reports how much space would be
1117 freed if GC were enabled. The page also shows how much disk space is
1118 present, used, reserved, and available for the Tahoe server, and
1119 whether the server is currently running in "read-write" mode or
1122 - When a directory node cannot be read (perhaps because of insufficent
1123 shares), a minimal webapi page is created so that the "more-info"
1124 links (including a Check/Repair operation) will still be accessible.
1126 - A new "reliability" page was added, with the beginnings of work on a
1127 statistical loss model. You can tell this page how many servers you
1128 are using and their independent failure probabilities, and it will
1129 tell you the likelihood that an arbitrary file will survive each
1130 repair period. The "numpy" package must be installed to access this
1131 page. A partial paper, written by Shawn Willden, has been added to
1132 docs/proposed/lossmodel.lyx .
1137 - "tahoe check" and "tahoe deep-check" now accept an "--add-lease"
1138 argument, to update a lease on all shares. This is the "mark" side
1139 of garbage collection.
1141 - In many cases, CLI error messages have been improved: the ugly
1142 HTMLized traceback has been replaced by a normal python traceback.
1144 - "tahoe deep-check" and "tahoe manifest" now have better error
1145 reporting. "tahoe cp" is now non-verbose by default.
1147 - "tahoe backup" now accepts several "--exclude" arguments, to ignore
1148 certain files (like editor temporary files and version-control
1149 metadata) during backup.
1151 - On windows, the CLI now accepts local paths like "c:\dir\file.txt",
1152 which previously was interpreted as a Tahoe path using a "c:" alias.
1154 - The "tahoe restart" command now uses "--force" by default (meaning
1155 it will start a node even if it didn't look like there was one
1158 - The "tahoe debug consolidate" command was added. This takes a series
1159 of independent timestamped snapshot directories (such as those
1160 created by the allmydata.com windows backup program, or a series of
1161 "tahoe cp -r" commands) and creates new snapshots that used shared
1162 read-only directories whenever possible (like the output of "tahoe
1163 backup"). In the most common case (when the snapshots are fairly
1164 similar), the result will use significantly fewer directories than
1165 the original, allowing "deep-check" and similar tools to run much
1166 faster. In some cases, the speedup can be an order of magnitude or
1167 more. This tool is still somewhat experimental, and only needs to
1168 be run on large backups produced by something other than "tahoe
1169 backup", so it was placed under the "debug" category.
1171 - "tahoe cp -r --caps-only tahoe:dir localdir" is a diagnostic tool
1172 which, instead of copying the full contents of files into the local
1173 directory, merely copies their filecaps. This can be used to verify
1174 the results of a "consolidation" operation.
1179 - The codebase no longer rauses RuntimeError as a kind of
1180 assert(). Specific exception classes were created for each previous
1181 instance of RuntimeError.
1183 -Many unit tests were changed to use a non-network test harness,
1184 speeding them up considerably.
1186 - Deep-traversal operations (manifest and deep-check) now walk
1187 individual directories in alphabetical order. Occasional turn breaks
1188 are inserted to prevent a stack overflow when traversing directories
1189 with hundreds of entries.
1191 - The experimental SFTP server had its path-handling logic changed
1192 slightly, to accomodate more SFTP clients, although there are still
1195 .. _#442: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/442
1196 .. _#645: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/645
1197 .. _garbage-collection.rst: docs/garbage-collection.rst
1199 Release 1.3.0 (2009-02-13)
1200 --------------------------
1202 Checker/Verifier/Repairer
1203 '''''''''''''''''''''''''
1205 - The primary focus of this release has been writing a checker /
1206 verifier / repairer for files and directories. "Checking" is the
1207 act of asking storage servers whether they have a share for the
1208 given file or directory: if there are not enough shares available,
1209 the file or directory will be unrecoverable. "Verifying" is the act
1210 of downloading and cryptographically asserting that the server's
1211 share is undamaged: it requires more work (bandwidth and CPU) than
1212 checking, but can catch problems that simple checking
1213 cannot. "Repair" is the act of replacing missing or damaged shares
1216 - This release includes a full checker, a partial verifier, and a
1217 partial repairer. The repairer is able to handle missing shares: new
1218 shares are generated and uploaded to make up for the missing
1219 ones. This is currently the best application of the repairer: to
1220 replace shares that were lost because of server departure or
1221 permanent drive failure.
1223 - The repairer in this release is somewhat able to handle corrupted
1224 shares. The limitations are:
1226 - Immutable verifier is incomplete: not all shares are used, and not
1227 all fields of those shares are verified. Therefore the immutable
1228 verifier has only a moderate chance of detecting corrupted shares.
1229 - The mutable verifier is mostly complete: all shares are examined,
1230 and most fields of the shares are validated.
1231 - The storage server protocol offers no way for the repairer to
1232 replace or delete immutable shares. If corruption is detected, the
1233 repairer will upload replacement shares to other servers, but the
1234 corrupted shares will be left in place.
1235 - read-only directories and read-only mutable files must be repaired
1236 by someone who holds the write-cap: the read-cap is
1237 insufficient. Moreover, the deep-check-and-repair operation will
1238 halt with an error if it attempts to repair one of these read-only
1240 - Some forms of corruption can cause both download and repair
1241 operations to fail. A future release will fix this, since download
1242 should be tolerant of any corruption as long as there are at least
1243 'k' valid shares, and repair should be able to fix any file that is
1246 - If the downloader, verifier, or repairer detects share corruption,
1247 the servers which provided the bad shares will be notified (via a
1248 file placed in the BASEDIR/storage/corruption-advisories directory)
1249 so their operators can manually delete the corrupted shares and
1250 investigate the problem. In addition, the "incident gatherer"
1251 mechanism will automatically report share corruption to an incident
1252 gatherer service, if one is configured. Note that corrupted shares
1253 indicate hardware failures, serious software bugs, or malice on the
1254 part of the storage server operator, so a corrupted share should be
1255 considered highly unusual.
1257 - By periodically checking/repairing all files and directories,
1258 objects in the Tahoe filesystem remain resistant to recoverability
1259 failures due to missing and/or broken servers.
1261 - This release includes a wapi mechanism to initiate checks on
1262 individual files and directories (with or without verification, and
1263 with or without automatic repair). A related mechanism is used to
1264 initiate a "deep-check" on a directory: recursively traversing the
1265 directory and its children, checking (and/or verifying/repairing)
1266 everything underneath. Both mechanisms can be run with an
1267 "output=JSON" argument, to obtain machine-readable check/repair
1268 status results. These results include a copy of the filesystem
1269 statistics from the "deep-stats" operation (including total number
1270 of files, size histogram, etc). If repair is possible, a "Repair"
1271 button will appear on the results page.
1273 - The client web interface now features some extra buttons to initiate
1274 check and deep-check operations. When these operations finish, they
1275 display a results page that summarizes any problems that were
1276 encountered. All long-running deep-traversal operations, including
1277 deep-check, use a start-and-poll mechanism, to avoid depending upon
1278 a single long-lived HTTP connection. `webapi.rst`_ has
1284 - The "tahoe backup" command is new in this release, which creates
1285 efficient versioned backups of a local directory. Given a local
1286 pathname and a target Tahoe directory, this will create a read-only
1287 snapshot of the local directory in $target/Archives/$timestamp. It
1288 will also create $target/Latest, which is a reference to the latest
1289 such snapshot. Each time you run "tahoe backup" with the same source
1290 and target, a new $timestamp snapshot will be added. These snapshots
1291 will share directories that have not changed since the last backup,
1292 to speed up the process and minimize storage requirements. In
1293 addition, a small database is used to keep track of which local
1294 files have been uploaded already, to avoid uploading them a second
1295 time. This drastically reduces the work needed to do a "null backup"
1296 (when nothing has changed locally), making "tahoe backup' suitable
1297 to run from a daily cronjob.
1299 Note that the "tahoe backup" CLI command must be used in conjunction
1300 with a 1.3.0-or-newer Tahoe client node; there was a bug in the
1301 1.2.0 webapi implementation that would prevent the last step (create
1302 $target/Latest) from working.
1307 - The 12GiB (approximate) immutable-file-size limitation is
1308 lifted. This release knows how to handle so-called "v2 immutable
1309 shares", which permit immutable files of up to about 18 EiB (about
1310 3*10^14). These v2 shares are created if the file to be uploaded is
1311 too large to fit into v1 shares. v1 shares are created if the file
1312 is small enough to fit into them, so that files created with
1313 tahoe-1.3.0 can still be read by earlier versions if they are not
1314 too large. Note that storage servers also had to be changed to
1315 support larger files, and this release is the first release in which
1316 they are able to do that. Clients will detect which servers are
1317 capable of supporting large files on upload and will not attempt to
1318 upload shares of a large file to a server which doesn't support it.
1323 - Tahoe now includes experimental FTP and SFTP servers. When
1324 configured with a suitable method to translate username+password
1325 into a root directory cap, it provides simple access to the virtual
1326 filesystem. Remember that FTP is completely unencrypted: passwords,
1327 filenames, and file contents are all sent over the wire in
1328 cleartext, so FTP should only be used on a local (127.0.0.1)
1329 connection. This feature is still in development: there are no unit
1330 tests yet, and behavior with respect to Unicode filenames is
1331 uncertain. Please see `FTP-and-SFTP.rst`_ for
1332 configuration details. (`#512`_, `#531`_)
1337 - This release adds the 'tahoe create-alias' command, which is a
1338 combination of 'tahoe mkdir' and 'tahoe add-alias'. This also allows
1339 you to start using a new tahoe directory without exposing its URI in
1340 the argv list, which is publicly visible (through the process table)
1341 on most unix systems. Thanks to Kevin Reid for bringing this issue
1344 - The single-argument form of "tahoe put" was changed to create an
1345 unlinked file. I.e. "tahoe put bar.txt" will take the contents of a
1346 local "bar.txt" file, upload them to the grid, and print the
1347 resulting read-cap; the file will not be attached to any
1348 directories. This seemed a bit more useful than the previous
1349 behavior (copy stdin, upload to the grid, attach the resulting file
1350 into your default tahoe: alias in a child named 'bar.txt').
1352 - "tahoe put" was also fixed to handle mutable files correctly: "tahoe
1353 put bar.txt URI:SSK:..." will read the contents of the local bar.txt
1354 and use them to replace the contents of the given mutable file.
1356 - The "tahoe webopen" command was modified to accept aliases. This
1357 means "tahoe webopen tahoe:" will cause your web browser to open to
1358 a "wui" page that gives access to the directory associated with the
1359 default "tahoe:" alias. It should also accept leading slashes, like
1360 "tahoe webopen tahoe:/stuff".
1362 - Many esoteric debugging commands were moved down into a "debug"
1365 - tahoe debug dump-cap
1366 - tahoe debug dump-share
1367 - tahoe debug find-shares
1368 - tahoe debug catalog-shares
1369 - tahoe debug corrupt-share
1371 The last command ("tahoe debug corrupt-share") flips a random bit
1372 of the given local sharefile. This is used to test the file
1373 verifying/repairing code, and obviously should not be used on user
1376 The cli might not correctly handle arguments which contain non-ascii
1377 characters in Tahoe v1.3 (although depending on your platform it
1378 might, especially if your platform can be configured to pass such
1379 characters on the command-line in utf-8 encoding). See
1380 https://tahoe-lafs.org/trac/tahoe-lafs/ticket/565 for details.
1385 - The "default webapi port", used when creating a new client node (and
1386 in the getting-started documentation), was changed from 8123 to
1387 3456, to reduce confusion when Tahoe accessed through a Firefox
1388 browser on which the "Torbutton" extension has been installed. Port
1389 8123 is occasionally used as a Tor control port, so Torbutton adds
1390 8123 to Firefox's list of "banned ports" to avoid CSRF attacks
1391 against Tor. Once 8123 is banned, it is difficult to diagnose why
1392 you can no longer reach a Tahoe node, so the Tahoe default was
1393 changed. Note that 3456 is reserved by IANA for the "vat" protocol,
1394 but there are argueably more Torbutton+Tahoe users than vat users
1395 these days. Note that this will only affect newly-created client
1396 nodes. Pre-existing client nodes, created by earlier versions of
1397 tahoe, may still be listening on 8123.
1399 - All deep-traversal operations (start-manifest, start-deep-size,
1400 start-deep-stats, start-deep-check) now use a start-and-poll
1401 approach, instead of using a single (fragile) long-running
1402 synchronous HTTP connection. All these "start-" operations use POST
1403 instead of GET. The old "GET manifest", "GET deep-size", and "POST
1404 deep-check" operations have been removed.
1406 - The new "POST start-manifest" operation, when it finally completes,
1407 results in a table of (path,cap), instead of the list of verifycaps
1408 produced by the old "GET manifest". The table is available in
1409 several formats: use output=html, output=text, or output=json to
1410 choose one. The JSON output also includes stats, and a list of
1411 verifycaps and storage-index strings. The "return_to=" and
1412 "when_done=" arguments have been removed from the t=check and
1413 deep-check operations.
1415 - The top-level status page (/status) now has a machine-readable form,
1416 via "/status/?t=json". This includes information about the
1417 currently-active uploads and downloads, which may be useful for
1418 frontends that wish to display progress information. There is no
1419 easy way to correlate the activities displayed here with recent wapi
1422 - Any files in BASEDIR/public_html/ (configurable) will be served in
1423 response to requests in the /static/ portion of the URL space. This
1424 will simplify the deployment of javascript-based frontends that can
1425 still access wapi calls by conforming to the (regrettable)
1426 "same-origin policy".
1428 - The welcome page now has a "Report Incident" button, which is tied
1429 into the "Incident Gatherer" machinery. If the node is attached to
1430 an incident gatherer (via log_gatherer.furl), then pushing this
1431 button will cause an Incident to be signalled: this means recent log
1432 events are aggregated and sent in a bundle to the gatherer. The user
1433 can push this button after something strange takes place (and they
1434 can provide a short message to go along with it), and the relevant
1435 data will be delivered to a centralized incident-gatherer for later
1436 processing by operations staff.
1438 - The "HEAD" method should now work correctly, in addition to the
1439 usual "GET", "PUT", and "POST" methods. "HEAD" is supposed to return
1440 exactly the same headers as "GET" would, but without any of the
1441 actual response body data. For mutable files, this now does a brief
1442 mapupdate (to figure out the size of the file that would be
1443 returned), without actually retrieving the file's contents.
1445 - The "GET" operation on files can now support the HTTP "Range:"
1446 header, allowing requests for partial content. This allows certain
1447 media players to correctly stream audio and movies out of a Tahoe
1448 grid. The current implementation uses a disk-based cache in
1449 BASEDIR/private/cache/download , which holds the plaintext of the
1450 files being downloaded. Future implementations might not use this
1451 cache. GET for immutable files now returns an ETag header.
1453 - Each file and directory now has a "Show More Info" web page, which
1454 contains much of the information that was crammed into the directory
1455 page before. This includes readonly URIs, storage index strings,
1456 object type, buttons to control checking/verifying/repairing, and
1457 deep-check/deep-stats buttons (for directories). For mutable files,
1458 the "replace contents" upload form has been moved here too. As a
1459 result, the directory page is now much simpler and cleaner, and
1460 several potentially-misleading links (like t=uri) are now gone.
1462 - Slashes are discouraged in Tahoe file/directory names, since they
1463 cause problems when accessing the filesystem through the
1464 wapi. However, there are a couple of accidental ways to generate
1465 such names. This release tries to make it easier to correct such
1466 mistakes by escaping slashes in several places, allowing slashes in
1467 the t=info and t=delete commands, and in the source (but not the
1468 target) of a t=rename command.
1473 - Tahoe's dependencies have been extended to require the
1474 "[secure_connections]" feature from Foolscap, which will cause
1475 pyOpenSSL to be required and/or installed. If OpenSSL and its
1476 development headers are already installed on your system, this can
1477 occur automatically. Tahoe now uses pollreactor (instead of the
1478 default selectreactor) to work around a bug between pyOpenSSL and
1479 the most recent release of Twisted (8.1.0). This bug only affects
1480 unit tests (hang during shutdown), and should not impact regular
1483 - The Tahoe source code tarballs now come in two different forms:
1484 regular and "sumo". The regular tarball contains just Tahoe, nothing
1485 else. When building from the regular tarball, the build process will
1486 download any unmet dependencies from the internet (starting with the
1487 index at PyPI) so it can build and install them. The "sumo" tarball
1488 contains copies of all the libraries that Tahoe requires (foolscap,
1489 twisted, zfec, etc), so using the "sumo" tarball should not require
1490 any internet access during the build process. This can be useful if
1491 you want to build Tahoe while on an airplane, a desert island, or
1492 other bandwidth-limited environments.
1494 - Similarly, tahoe-lafs.org now hosts a "tahoe-deps" tarball which
1495 contains the latest versions of all these dependencies. This
1497 https://tahoe-lafs.org/source/tahoe/deps/tahoe-deps.tar.gz, can be
1498 unpacked in the tahoe source tree (or in its parent directory), and
1499 the build process should satisfy its downloading needs from it
1500 instead of reaching out to PyPI. This can be useful if you want to
1501 build Tahoe from a darcs checkout while on that airplane or desert
1504 - Because of the previous two changes ("sumo" tarballs and the
1505 "tahoe-deps" bundle), most of the files have been removed from
1506 misc/dependencies/ . This brings the regular Tahoe tarball down to
1507 2MB (compressed), and the darcs checkout (without history) to about
1508 7.6MB. A full darcs checkout will still be fairly large (because of
1509 the historical patches which included the dependent libraries), but
1510 a 'lazy' one should now be small.
1512 - The default "make" target is now an alias for "setup.py build",
1513 which itself is an alias for "setup.py develop --prefix support",
1514 with some extra work before and after (see setup.cfg). Most of the
1515 complicated platform-dependent code in the Makefile was rewritten in
1516 Python and moved into setup.py, simplifying things considerably.
1518 - Likewise, the "make test" target now delegates most of its work to
1519 "setup.py test", which takes care of getting PYTHONPATH configured
1520 to access the tahoe code (and dependencies) that gets put in
1521 support/lib/ by the build_tahoe step. This should allow unit tests
1522 to be run even when trial (which is part of Twisted) wasn't already
1523 installed (in this case, trial gets installed to support/bin because
1524 Twisted is a dependency of Tahoe).
1526 - Tahoe is now compatible with the recently-released Python 2.6 ,
1527 although it is recommended to use Tahoe on Python 2.5, on which it
1528 has received more thorough testing and deployment.
1530 - Tahoe is now compatible with simplejson-2.0.x . The previous release
1531 assumed that simplejson.loads always returned unicode strings, which
1532 is no longer the case in 2.0.x .
1534 Grid Management Tools
1535 '''''''''''''''''''''
1537 - Several tools have been added or updated in the misc/ directory,
1538 mostly munin plugins that can be used to monitor a storage grid.
1540 - The misc/spacetime/ directory contains a "disk watcher" daemon
1541 (startable with 'tahoe start'), which can be configured with a set
1542 of HTTP URLs (pointing at the wapi '/statistics' page of a bunch of
1543 storage servers), and will periodically fetch
1544 disk-used/disk-available information from all the servers. It keeps
1545 this information in an Axiom database (a sqlite-based library
1546 available from divmod.org). The daemon computes time-averaged rates
1547 of disk usage, as well as a prediction of how much time is left
1548 before the grid is completely full.
1550 - The misc/munin/ directory contains a new set of munin plugins
1551 (tahoe_diskleft, tahoe_diskusage, tahoe_doomsday) which talk to the
1552 disk-watcher and provide graphs of its calculations.
1554 - To support the disk-watcher, the Tahoe statistics component
1555 (visible through the wapi at the /statistics/ URL) now includes
1556 disk-used and disk-available information. Both are derived through
1557 an equivalent of the unix 'df' command (i.e. they ask the kernel
1558 for the number of free blocks on the partition that encloses the
1559 BASEDIR/storage directory). In the future, the disk-available
1560 number will be further influenced by the local storage policy: if
1561 that policy says that the server should refuse new shares when less
1562 than 5GB is left on the partition, then "disk-available" will
1563 report zero even though the kernel sees 5GB remaining.
1565 - The 'tahoe_overhead' munin plugin interacts with an
1566 allmydata.com-specific server which reports the total of the
1567 'deep-size' reports for all active user accounts, compares this
1568 with the disk-watcher data, to report on overhead percentages. This
1569 provides information on how much space could be recovered once
1570 Tahoe implements some form of garbage collection.
1572 Configuration Changes: single INI-format tahoe.cfg file
1573 '''''''''''''''''''''''''''''''''''''''''''''''''''''''
1575 - The Tahoe node is now configured with a single INI-format file,
1576 named "tahoe.cfg", in the node's base directory. Most of the
1577 previous multiple-separate-files are still read for backwards
1578 compatibility (the embedded SSH debug server and the
1579 advertised_ip_addresses files are the exceptions), but new
1580 directives will only be added to tahoe.cfg . The "tahoe
1581 create-client" command will create a tahoe.cfg for you, with sample
1582 values commented out. (ticket `#518`_)
1584 - tahoe.cfg now has controls for the foolscap "keepalive" and
1585 "disconnect" timeouts (`#521`_).
1587 - tahoe.cfg now has controls for the encoding parameters:
1588 "shares.needed" and "shares.total" in the "[client]" section. The
1589 default parameters are still 3-of-10.
1591 - The inefficient storage 'sizelimit' control (which established an
1592 upper bound on the amount of space that a storage server is allowed
1593 to consume) has been replaced by a lightweight 'reserved_space'
1594 control (which establishes a lower bound on the amount of remaining
1595 space). The storage server will reject all writes that would cause
1596 the remaining disk space (as measured by a '/bin/df' equivalent) to
1597 drop below this value. The "[storage]reserved_space=" tahoe.cfg
1598 parameter controls this setting. (note that this only affects
1599 immutable shares: it is an outstanding bug that reserved_space does
1600 not prevent the allocation of new mutable shares, nor does it
1601 prevent the growth of existing mutable shares).
1606 - Clients now declare which versions of the protocols they
1607 support. This is part of a new backwards-compatibility system:
1608 https://tahoe-lafs.org/trac/tahoe-lafs/wiki/Versioning .
1610 - The version strings for human inspection (as displayed on the
1611 Welcome web page, and included in logs) now includes a platform
1612 identifer (frequently including a linux distribution name, processor
1615 - Several bugs have been fixed, including one that would cause an
1616 exception (in the logs) if a wapi download operation was cancelled
1617 (by closing the TCP connection, or pushing the "stop" button in a
1620 - Tahoe now uses Foolscap "Incidents", writing an "incident report"
1621 file to logs/incidents/ each time something weird occurs. These
1622 reports are available to an "incident gatherer" through the flogtool
1623 command. For more details, please see the Foolscap logging
1624 documentation. An incident-classifying plugin function is provided
1625 in misc/incident-gatherer/classify_tahoe.py .
1627 - If clients detect corruption in shares, they now automatically
1628 report it to the server holding that share, if it is new enough to
1629 accept the report. These reports are written to files in
1630 BASEDIR/storage/corruption-advisories .
1632 - The 'nickname' setting is now defined to be a UTF-8 -encoded string,
1633 allowing non-ascii nicknames.
1635 - The 'tahoe start' command will now accept a --syslog argument and
1636 pass it through to twistd, making it easier to launch non-Tahoe
1637 nodes (like the cpu-watcher) and have them log to syslogd instead of
1638 a local file. This is useful when running a Tahoe node out of a USB
1641 - The Mac GUI in src/allmydata/gui/ has been improved.
1643 .. _#512: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/512
1644 .. _#518: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/518
1645 .. _#521: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/521
1646 .. _#531: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/531
1648 Release 1.2.0 (2008-07-21)
1649 --------------------------
1654 - This release makes the immutable-file "ciphertext hash tree"
1655 mandatory. Previous releases allowed the uploader to decide whether
1656 their file would have an integrity check on the ciphertext or not. A
1657 malicious uploader could use this to create a readcap that would
1658 download as one file or a different one, depending upon which shares
1659 the client fetched first, with no errors raised. There are other
1660 integrity checks on the shares themselves, preventing a storage
1661 server or other party from violating the integrity properties of the
1662 read-cap: this failure was only exploitable by the uploader who
1663 gives you a carefully constructed read-cap. If you download the file
1664 with Tahoe 1.2.0 or later, you will not be vulnerable to this
1667 This change does not introduce a compatibility issue, because all
1668 existing versions of Tahoe will emit the ciphertext hash tree in
1674 - Tahoe now requires Foolscap-0.2.9 . It also requires pycryptopp 0.5
1675 or newer, since earlier versions had a bug that interacted with
1676 specific compiler versions that could sometimes result in incorrect
1677 encryption behavior. Both packages are included in the Tahoe source
1678 tarball in misc/dependencies/ , and should be built automatically
1684 - Web API directory pages should now contain properly-slash-terminated
1685 links to other directories. They have also stopped using absolute
1686 links in forms and pages (which interfered with the use of a
1687 front-end load-balancing proxy).
1689 - The behavior of the "Check This File" button changed, in conjunction
1690 with larger internal changes to file checking/verification. The
1691 button triggers an immediate check as before, but the outcome is
1692 shown on its own page, and does not get stored anywhere. As a
1693 result, the web directory page no longer shows historical checker
1696 - A new "Deep-Check" button has been added, which allows a user to
1697 initiate a recursive check of the given directory and all files and
1698 directories reachable from it. This can cause quite a bit of work,
1699 and has no intermediate progress information or feedback about the
1700 process. In addition, the results of the deep-check are extremely
1701 limited. A later release will improve this behavior.
1703 - The web server's behavior with respect to non-ASCII (unicode)
1704 filenames in the "GET save=true" operation has been improved. To
1705 achieve maximum compatibility with variously buggy web browsers, the
1706 server does not try to figure out the character set of the inbound
1707 filename. It just echoes the same bytes back to the browser in the
1708 Content-Disposition header. This seems to make both IE7 and Firefox
1711 Checker/Verifier/Repairer
1712 '''''''''''''''''''''''''
1714 - Tahoe is slowly acquiring convenient tools to check up on file
1715 health, examine existing shares for errors, and repair files that
1716 are not fully healthy. This release adds a mutable
1717 checker/verifier/repairer, although testing is very limited, and
1718 there are no web interfaces to trigger repair yet. The "Check"
1719 button next to each file or directory on the wapi page will perform
1720 a file check, and the "deep check" button on each directory will
1721 recursively check all files and directories reachable from there
1722 (which may take a very long time).
1724 Future releases will improve access to this functionality.
1726 Operations/Packaging
1727 ''''''''''''''''''''
1729 - A "check-grid" script has been added, along with a Makefile
1730 target. This is intended (with the help of a pre-configured node
1731 directory) to check upon the health of a Tahoe grid, uploading and
1732 downloading a few files. This can be used as a monitoring tool for a
1733 deployed grid, to be run periodically and to signal an error if it
1734 ever fails. It also helps with compatibility testing, to verify that
1735 the latest Tahoe code is still able to handle files created by an
1738 - The munin plugins from misc/munin/ are now copied into any generated
1739 debian packages, and are made executable (and uncompressed) so they
1740 can be symlinked directly from /etc/munin/plugins/ .
1742 - Ubuntu "Hardy" was added as a supported debian platform, with a
1743 Makefile target to produce hardy .deb packages. Some notes have been
1744 added to `debian.rst`_ about building Tahoe on a debian/ubuntu
1747 - Storage servers now measure operation rates and
1748 latency-per-operation, and provides results through the /statistics
1749 web page as well as the stats gatherer. Munin plugins have been
1755 - Tahoe nodes now use Foolscap "incident logging" to record unusual
1756 events to their NODEDIR/logs/incidents/ directory. These incident
1757 files can be examined by Foolscap logging tools, or delivered to an
1758 external log-gatherer for further analysis. Note that Tahoe now
1759 requires Foolscap-0.2.9, since 0.2.8 had a bug that complained about
1760 "OSError: File exists" when trying to create the incidents/
1761 directory for a second time.
1763 - If no servers are available when retrieving a mutable file (like a
1764 directory), the node now reports an error instead of hanging
1765 forever. Earlier releases would not only hang (causing the wapi
1766 directory listing to get stuck half-way through), but the internal
1767 dirnode serialization would cause all subsequent attempts to
1768 retrieve or modify the same directory to hang as well. `#463`_
1770 - A minor internal exception (reported in logs/twistd.log, in the
1771 "stopProducing" method) was fixed, which complained about
1772 "self._paused_at not defined" whenever a file download was stopped
1773 from the web browser end.
1775 .. _#463: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/463
1776 .. _#491: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/491
1777 .. _debian.rst: docs/debian.rst
1779 Release 1.1.0 (2008-06-11)
1780 --------------------------
1782 CLI: new "alias" model
1783 ''''''''''''''''''''''
1785 - The new CLI code uses an scp/rsync -like interface, in which
1786 directories in the Tahoe storage grid are referenced by a
1787 colon-suffixed alias. The new commands look like:
1789 - tahoe cp local.txt tahoe:virtual.txt
1790 - tahoe ls work:subdir
1792 - More functionality is available through the CLI: creating unlinked
1793 files and directories, recursive copy in or out of the storage grid,
1794 hardlinks, and retrieving the raw read- or write- caps through the
1795 'ls' command. Please read `CLI.rst`_ for complete details.
1797 wapi: new pages, new commands
1798 '''''''''''''''''''''''''''''
1800 - Several new pages were added to the web API:
1802 - /helper_status : to describe what a Helper is doing
1803 - /statistics : reports node uptime, CPU usage, other stats
1804 - /file : for easy file-download URLs, see `#221`_
1805 - /cap == /uri : future compatibility
1807 - The localdir=/localfile= and t=download operations were
1808 removed. These required special configuration to enable anyways, but
1809 this feature was a security problem, and was mostly obviated by the
1810 new "cp -r" command.
1812 - Several new options to the GET command were added:
1814 - t=deep-size : add up the size of all immutable files reachable from the directory
1815 - t=deep-stats : return a JSON-encoded description of number of files, size distribution, total size, etc
1817 - POST is now preferred over PUT for most operations which cause
1820 - Most wapi calls now accept overwrite=, and default to overwrite=true
1822 - "POST /uri/DIRCAP/parent/child?t=mkdir" is now the preferred API to
1823 create multiple directories at once, rather than ...?t=mkdir-p .
1825 - PUT to a mutable file ("PUT /uri/MUTABLEFILECAP", "PUT
1826 /uri/DIRCAP/child") will modify the file in-place.
1828 - more munin graphs in misc/munin/
1831 - tahoe-rootdir-space
1832 - tahoe_estimate_files
1833 - mutable files published/retrieved
1842 - setuptools (now required at runtime)
1844 New Mutable-File Code
1845 '''''''''''''''''''''
1847 - The mutable-file handling code (mostly used for directories) has
1848 been completely rewritten. The new scheme has a better API (with a
1849 modify() method) and is less likely to lose data when several
1850 uncoordinated writers change a file at the same time.
1852 - In addition, a single Tahoe process will coordinate its own
1853 writes. If you make two concurrent directory-modifying wapi calls to
1854 a single tahoe node, it will internally make one of them wait for
1855 the other to complete. This prevents auto-collision (`#391`_).
1857 - The new mutable-file code also detects errors during publish
1858 better. Earlier releases might believe that a mutable file was
1859 published when in fact it failed.
1864 - The node now monitors its own CPU usage, as a percentage, measured
1865 every 60 seconds. 1/5/15 minute moving averages are available on the
1866 /statistics web page and via the stats-gathering interface.
1868 - Clients now accelerate reconnection to all servers after being
1869 offline (`#374`_). When a client is offline for a long time, it
1870 scales back reconnection attempts to approximately once per hour, so
1871 it may take a while to make the first attempt, but once any attempt
1872 succeeds, the other server connections will be retried immediately.
1874 - A new "offloaded KeyGenerator" facility can be configured, to move
1875 RSA key generation out from, say, a wapi node, into a separate
1876 process. RSA keys can take several seconds to create, and so a wapi
1877 node which is being used for directory creation will be unavailable
1878 for anything else during this time. The Key Generator process will
1879 pre-compute a small pool of keys, to speed things up further. This
1880 also takes better advantage of multi-core CPUs, or SMP hosts.
1882 - The node will only use a potentially-slow "du -s" command at startup
1883 (to measure how much space has been used) if the "sizelimit"
1884 parameter has been configured (to limit how much space is
1885 used). Large storage servers should turn off sizelimit until a later
1886 release improves the space-management code, since "du -s" on a
1887 terabyte filesystem can take hours.
1889 - The Introducer now allows new announcements to replace old ones, to
1890 avoid buildups of obsolete announcements.
1892 - Immutable files are limited to about 12GiB (when using the default
1893 3-of-10 encoding), because larger files would be corrupted by the
1894 four-byte share-size field on the storage servers (`#439`_). A later
1895 release will remove this limit. Earlier releases would allow >12GiB
1896 uploads, but the resulting file would be unretrievable.
1898 - The docs/ directory has been rearranged, with old docs put in
1899 docs/historical/ and not-yet-implemented ones in docs/proposed/ .
1901 - The Mac OS-X FUSE plugin has a significant bug fix: earlier versions
1902 would corrupt writes that used seek() instead of writing the file in
1903 linear order. The rsync tool is known to perform writes in this
1904 order. This has been fixed.
1906 .. _#221: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/221
1907 .. _#374: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/374
1908 .. _#391: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/391
1909 .. _#439: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/439
1910 .. _CLI.rst: docs/CLI.rst