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