2 ==================================
3 User-Visible Changes in Tahoe-LAFS
4 ==================================
6 Release 1.9.0 (2011-10-30)
7 --------------------------
12 - The most significant new feature in this release is MDMF: "Medium-size
13 Distributed Mutable Files". Unlike standard SDMF files, these provide
14 efficient partial-access (reading and modifying small portions of the file
15 instead of the whole thing). MDMF is opt-in (it is not yet the default
16 format for mutable files), both to ensure compatibility with previous
17 versions, and because the algorithm does not yet meet memory-usage goals.
18 Enable it with ``--format=MDMF`` in the CLI (``tahoe put`` and ``tahoe
19 mkdir``), or the "format" radioboxes in the web interface. See
20 `<docs/specifications/mutable.rst>`_ for more details (`#393`_, `#1507`_)
21 - A "blacklist" feature allows blocking access to specific files through
22 a particular gateway. See the "Access Blacklist" section of
23 `<docs/configuration.rst>`_ for more details. (`#1425`_)
24 - A "drop-upload" feature has been added, which allows you to upload
25 files to a Tahoe-LAFS directory just by writing them to a local
26 directory. This feature is experimental and should not be relied on
27 to store the only copy of valuable data. It is currently available
28 only on Linux. See `<docs/frontends/drop-upload.rst>`_ for documentation.
30 - The timeline of immutable downloads can be viewed using a zoomable and
31 pannable JavaScript-based visualization. This is accessed using the
32 'timeline' link on the File Download Status page for the download, which
33 can be reached from the Recent Uploads and Downloads page.
35 Configuration/Behavior Changes
36 ''''''''''''''''''''''''''''''
38 - Prior to Tahoe-LAFS v1.3, the configuration of some node options could
39 be specified using individual config files rather than via ``tahoe.cfg``.
40 These files now cause an error if present. (`#1385`_)
41 - Storage servers now calculate their remaining space based on the filesystem
42 containing the ``storage/shares/`` directory. Previously they looked at the
43 filesystem containing the ``storage/`` directory. This allows
44 ``storage/shares/``, rather than ``storage/``, to be a mount point or a
45 symlink pointing to another filesystem. (`#1384`_)
46 - ``tahoe cp xyz MUTABLE`` will modify the existing mutable file instead of
47 creating a new one. (`#1304`_)
48 - The button for unlinking a file from its directory on a WUI directory
49 listing is now labelled "unlink" rather than "del". (`#1104`_)
54 - The security bugfix for the vulnerability allowing deletion of shares,
55 detailed in the news for v1.8.3 below, is also included in this
57 - Some cases of immutable upload, for example using the ``tahoe put`` and
58 ``tahoe cp`` commands or SFTP, did not appear in the history of Recent
59 Uploads and Downloads. (`#1079`_)
60 - The memory footprint of the verifier has been reduced by serializing
61 block fetches. (`#1395`_)
62 - Large immutable downloads are now a little faster than in v1.8.3 (about
63 5% on a fast network). (`#1268`_)
68 - The files related to Debian packaging have been removed from the Tahoe
69 source tree, since they are now maintained as part of the official
70 Debian packages. (`#1454`_)
71 - The unmaintained FUSE plugins were removed from the source tree. See
72 ``docs/frontends/FTP-and-SFTP.rst`` for how to mount a Tahoe filesystem on
73 Unix via sshfs. (`#1409`_)
74 - The Tahoe licenses now give explicit permission to combine Tahoe-LAFS
75 with code distributed under the following additional open-source licenses
76 (any version of each):
78 * Academic Free License
79 * Apple Public Source License
80 * BitTorrent Open Source License
81 * Lucent Public License
82 * Jabber Open Source License
83 * Common Development and Distribution License
84 * Microsoft Public License
85 * Microsoft Reciprocal License
86 * Sun Industry Standards Source License
87 * Open Software License
89 Compatibility and Dependencies
90 ''''''''''''''''''''''''''''''
92 - To resolve an incompatibility between Nevow and zope.interface (versions
93 3.6.3 and 3.6.4), Tahoe-LAFS now requires an earlier or later
94 version of zope.interface. (`#1435`_)
95 - The Twisted dependency has been raised to version 10.1 to ensure we no
96 longer require pywin32 on Windows, the new drop-upload feature has the
97 required support from Twisted on Linux, and that it is never necessary to
98 patch Twisted in order to use the FTP frontend. (`#1274`_, `#1429`_,
100 - An explicit dependency on pyOpenSSL has been added, replacing the indirect
101 dependency via the "secure_connections" option of foolscap. (`#1383`_)
106 - A ``man`` page has been added (`#1420`_). All other docs are in ReST
108 - The ``tahoe_files`` munin plugin reported an incorrect count of the number
109 of share files. (`#1391`_)
110 - Minor documentation updates: #627, #1104, #1225, #1297, #1342, #1404
111 - Other minor changes: #636, #1355, #1363, #1366, #1388, #1392, #1412, #1344,
112 #1347, #1359, #1389, #1441, #1442, #1446, #1474, #1503
114 .. _`#393`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/393
115 .. _`#1079`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1079
116 .. _`#1104`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1104
117 .. _`#1268`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1268
118 .. _`#1274`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1274
119 .. _`#1304`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1304
120 .. _`#1355`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1355
121 .. _`#1383`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1383
122 .. _`#1384`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1384
123 .. _`#1385`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1385
124 .. _`#1388`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1388
125 .. _`#1391`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1391
126 .. _`#1392`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1392
127 .. _`#1395`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1395
128 .. _`#1409`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1409
129 .. _`#1420`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1420
130 .. _`#1425`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1425
131 .. _`#1429`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1429
132 .. _`#1435`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1435
133 .. _`#1438`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1438
134 .. _`#1454`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1454
135 .. _`#1507`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1507
138 Release 1.8.3 (2011-09-13)
139 --------------------------
141 Security-related Bugfix
142 '''''''''''''''''''''''
144 - Fix flaw that would allow a person who knows a storage index of a file to
145 delete shares of that file. (`#1528`_)
146 - Remove corner cases in mutable file bounds management which could expose
147 extra lease info or old share data (from prior versions of the mutable
148 file) if someone with write authority to that mutable file exercised these
149 corner cases in a way that no actual Tahoe-LAFS client does. (Probably not
150 exploitable.) (`#1528`_)
152 .. _`#1528`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1528
155 Release 1.8.2 (2011-01-30)
156 --------------------------
158 Compatibility and Dependencies
159 ''''''''''''''''''''''''''''''
161 - Tahoe is now compatible with Twisted-10.2 (released last month), as
162 well as with earlier versions. The previous Tahoe-1.8.1 release
163 failed to run against Twisted-10.2, raising an AttributeError on
164 StreamServerEndpointService (`#1286`_)
165 - Tahoe now depends upon the "mock" testing library, and the foolscap
166 dependency was raised to 0.6.1 . It no longer requires pywin32
167 (which was used only on windows). Future developers should note that
168 reactor.spawnProcess and derivatives may no longer be used inside
174 - the default reserved_space value for new storage nodes is 1 GB
176 - documentation is now in reStructuredText (.rst) format
177 - "tahoe cp" should now handle non-ASCII filenames
178 - the unmaintained Mac/Windows GUI applications have been removed
180 - tahoe processes should appear in top and ps as "tahoe", not
181 "python", on some unix platforms. (`#174`_)
182 - "tahoe debug trial" can be used to run the test suite (`#1296`_)
183 - the SFTP frontend now reports unknown sizes as "0" instead of "?",
184 to improve compatibility with clients like FileZilla (`#1337`_)
185 - "tahoe --version" should now report correct values in situations
186 where 1.8.1 might have been wrong (`#1287`_)
188 .. _`#174`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/174
189 .. _`#1208`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1208
190 .. _`#1282`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1282
191 .. _`#1286`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1286
192 .. _`#1287`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1287
193 .. _`#1296`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1296
194 .. _`#1337`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1337
197 Release 1.8.1 (2010-10-28)
198 --------------------------
200 Bugfixes and Improvements
201 '''''''''''''''''''''''''
203 - Allow the repairer to improve the health of a file by uploading some
204 shares, even if it cannot achieve the configured happiness
205 threshold. This fixes a regression introduced between v1.7.1 and
207 - Fix a memory leak in the ResponseCache which is used during mutable
208 file/directory operations. (`#1045`_)
209 - Fix a regression and add a performance improvement in the
210 downloader. This issue caused repair to fail in some special
212 - Fix a bug that caused 'tahoe cp' to fail for a grid-to-grid copy
213 involving a non-ASCII filename. (`#1224`_)
214 - Fix a rarely-encountered bug involving printing large strings to the
215 console on Windows. (`#1232`_)
216 - Perform ~ expansion in the --exclude-from filename argument to
217 'tahoe backup'. (`#1241`_)
218 - The CLI's 'tahoe mv' and 'tahoe ln' commands previously would try to
219 use an HTTP proxy if the HTTP_PROXY environment variable was set.
220 These now always connect directly to the WAPI, thus avoiding giving
221 caps to the HTTP proxy (and also avoiding failures in the case that
222 the proxy is failing or requires authentication). (`#1253`_)
223 - The CLI now correctly reports failure in the case that 'tahoe mv'
224 fails to unlink the file from its old location. (`#1255`_)
225 - 'tahoe start' now gives a more positive indication that the node has
227 - The arguments seen by 'ps' or other tools for node processes are now
228 more useful (in particular, they include the path of the 'tahoe'
229 script, rather than an obscure tool named 'twistd'). (`#174`_)
234 - The tahoe start/stop/restart and node creation commands no longer
235 accept the -m or --multiple option, for consistency between
236 platforms. (`#1262`_)
241 - We now host binary packages so that users on certain operating
242 systems can install without having a compiler.
243 <https://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-lafs-dep-eggs/README.html>
244 - Use a newer version of a dependency if needed, even if an older
245 version is installed. This would previously cause a VersionConflict
247 - Use a precompiled binary of a dependency if one with a sufficiently
248 high version number is available, instead of attempting to compile
249 the dependency from source, even if the source version has a higher
250 version number. (`#1233`_)
255 - All current documentation in .txt format has been converted to .rst
257 - Added docs/backdoors.rst declaring that we won't add backdoors to
258 Tahoe-LAFS, or add anything to facilitate government access to data.
261 .. _`#71`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/71
262 .. _`#174`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/174
263 .. _`#1212`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1212
264 .. _`#1045`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1045
265 .. _`#1190`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1190
266 .. _`#1216`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1216
267 .. _`#1223`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1223
268 .. _`#1224`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1224
269 .. _`#1225`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1225
270 .. _`#1232`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1232
271 .. _`#1233`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1233
272 .. _`#1241`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1241
273 .. _`#1253`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1253
274 .. _`#1255`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1255
275 .. _`#1262`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1262
278 Release 1.8.0 (2010-09-23)
279 --------------------------
284 - A completely new downloader which improves performance and
285 robustness of immutable-file downloads. It uses the fastest K
286 servers to download the data in K-way parallel. It automatically
287 fails over to alternate servers if servers fail in mid-download. It
288 allows seeking to arbitrary locations in the file (the previous
289 downloader which would only read the entire file sequentially from
290 beginning to end). It minimizes unnecessary round trips and
291 unnecessary bytes transferred to improve performance. It sends
292 requests to fewer servers to reduce the load on servers (the
293 previous one would send a small request to every server for every
294 download) (`#287`_, `#288`_, `#448`_, `#798`_, `#800`_, `#990`_,
296 - Non-ASCII command-line arguments and non-ASCII outputs now work on
297 Windows. In addition, the command-line tool now works on 64-bit
300 Bugfixes and Improvements
301 '''''''''''''''''''''''''
303 - Document and clean up the command-line options for specifying the
304 node's base directory. (`#188`_, `#706`_, `#715`_, `#772`_,
306 - The default node directory for Windows is ".tahoe" in the user's
307 home directory, the same as on other platforms. (`#890`_)
308 - Fix a case in which full cap URIs could be logged. (`#685`_,
310 - Fix bug in WUI in Python 2.5 when the system clock is set back to
311 1969. Now you can use Tahoe-LAFS with Python 2.5 and set your system
312 clock to 1969 and still use the WUI. (`#1055`_)
313 - Many improvements in code organization, tests, logging,
314 documentation, and packaging. (`#983`_, `#1074`_, `#1108`_,
315 `#1127`_, `#1129`_, `#1131`_, `#1166`_, `#1175`_)
320 - on x86 and x86-64 platforms, pycryptopp >= 0.5.20
321 - pycrypto 2.2 is excluded due to a bug
323 .. _`#188`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/188
324 .. _`#287`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/287
325 .. _`#288`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/288
326 .. _`#448`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/448
327 .. _`#685`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/685
328 .. _`#706`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/706
329 .. _`#715`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/715
330 .. _`#772`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/772
331 .. _`#798`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/798
332 .. _`#800`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/800
333 .. _`#890`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/890
334 .. _`#983`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/983
335 .. _`#990`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/990
336 .. _`#1055`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1055
337 .. _`#1074`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1074
338 .. _`#1108`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1108
339 .. _`#1155`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1155
340 .. _`#1170`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1170
341 .. _`#1191`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1191
342 .. _`#1127`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1127
343 .. _`#1129`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1129
344 .. _`#1131`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1131
345 .. _`#1166`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1166
346 .. _`#1175`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1175
348 Release 1.7.1 (2010-07-18)
349 --------------------------
351 Bugfixes and Improvements
352 '''''''''''''''''''''''''
354 - Fix bug in which uploader could fail with AssertionFailure or report
355 that it had achieved servers-of-happiness when it hadn't. (`#1118`_)
356 - Fix bug in which servers could get into a state where they would
357 refuse to accept shares of a certain file (`#1117`_)
358 - Add init scripts for managing the gateway server on Debian/Ubuntu
360 - Fix bug where server version number was always 0 on the welcome page
362 - Add new command-line command "tahoe unlink" as a synonym for "tahoe
364 - The FTP frontend now encrypts its temporary files, protecting their
365 contents from an attacker who is able to read the disk. (`#1083`_)
366 - Fix IP address detection on FreeBSD 7, 8, and 9 (`#1098`_)
367 - Fix minor layout issue in the Web User Interface with Internet
369 - Fix rarely-encountered incompatibility between Twisted logging
370 utility and the new unicode support added in v1.7.0 (`#1099`_)
371 - Forward-compatibility improvements for non-ASCII caps (`#1051`_)
376 - Simplify and tidy-up directories, unicode support, test code
377 (`#923`_, `#967`_, `#1072`_)
379 .. _`#776`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/776
380 .. _`#923`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/923
381 .. _`#961`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/961
382 .. _`#967`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/967
383 .. _`#1051`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1051
384 .. _`#1067`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1067
385 .. _`#1072`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1072
386 .. _`#1083`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1083
387 .. _`#1097`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1097
388 .. _`#1098`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1098
389 .. _`#1099`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1099
390 .. _`#1117`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1117
391 .. _`#1118`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1118
394 Release 1.7.0 (2010-06-18)
395 --------------------------
400 - SFTP support (`#1037`_)
401 Your Tahoe-LAFS gateway now acts like a full-fledged SFTP server. It
402 has been tested with sshfs to provide a virtual filesystem in Linux.
403 Many users have asked for this feature. We hope that it serves them
404 well! See the `FTP-and-SFTP.rst`_ document to get
406 - support for non-ASCII character encodings (`#534`_)
407 Tahoe-LAFS now correctly handles filenames containing non-ASCII
408 characters on all supported platforms:
410 - when reading files in from the local filesystem (such as when you
411 run "tahoe backup" to back up your local files to a Tahoe-LAFS
413 - when writing files out to the local filesystem (such as when you
414 run "tahoe cp -r" to recursively copy files out of a Tahoe-LAFS
416 - when displaying filenames to the terminal (such as when you run
417 "tahoe ls"), subject to limitations of the terminal and locale;
418 - when parsing command-line arguments, except on Windows.
420 - Servers of Happiness (`#778`_)
421 Tahoe-LAFS now measures during immutable file upload to see how well
422 distributed it is across multiple servers. It aborts the upload if
423 the pieces of the file are not sufficiently well-distributed.
424 This behavior is controlled by a configuration parameter called
425 "servers of happiness". With the default settings for its erasure
426 coding, Tahoe-LAFS generates 10 shares for each file, such that any
427 3 of those shares are sufficient to recover the file. The default
428 value of "servers of happiness" is 7, which means that Tahoe-LAFS
429 will guarantee that there are at least 7 servers holding some of the
430 shares, such that any 3 of those servers can completely recover your
431 file. The new upload code also distributes the shares better than the
432 previous version in some cases and takes better advantage of
433 pre-existing shares (when a file has already been previously
434 uploaded). See the `architecture.rst`_ document [3] for details.
436 Bugfixes and Improvements
437 '''''''''''''''''''''''''
439 - Premature abort of upload if some shares were already present and
440 some servers fail. (`#608`_)
441 - python ./setup.py install -- can't create or remove files in install
443 - Network failure => internal TypeError. (`#902`_)
444 - Install of Tahoe on CentOS 5.4. (`#933`_)
445 - CLI option --node-url now supports https url. (`#1028`_)
446 - HTML/CSS template files were not correctly installed under
448 - MetadataSetter does not enforce restriction on setting "tahoe"
450 - ImportError: No module named
451 setuptools_darcs.setuptools_darcs. (`#1054`_)
452 - Renamed Title in xhtml files. (`#1062`_)
453 - Increase Python version dependency to 2.4.4, to avoid a critical
454 CPython security bug. (`#1066`_)
455 - Typo correction for the munin plugin tahoe_storagespace. (`#968`_)
456 - Fix warnings found by pylint. (`#973`_)
457 - Changing format of some documentation files. (`#1027`_)
458 - the misc/ directory was tied up. (`#1068`_)
459 - The 'ctime' and 'mtime' metadata fields are no longer written except
460 by "tahoe backup". (`#924`_)
461 - Unicode filenames in Tahoe-LAFS directories are normalized so that
462 names that differ only in how accents are encoded are treated as the
464 - Various small improvements to documentation. (`#937`_, `#911`_,
470 - The 'tahoe debug consolidate' subcommand (for converting old
471 allmydata Windows client backups to a newer format) has been
477 - the Python version dependency is raised to 2.4.4 in some cases
478 (2.4.3 for Redhat-based Linux distributions, 2.4.2 for UCS-2 builds)
482 - mock (only required by unit tests)
484 .. _`#534`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/534
485 .. _`#608`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/608
486 .. _`#778`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/778
487 .. _`#803`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/803
488 .. _`#902`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/902
489 .. _`#911`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/911
490 .. _`#924`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/924
491 .. _`#937`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/937
492 .. _`#933`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/933
493 .. _`#968`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/968
494 .. _`#973`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/973
495 .. _`#1024`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1024
496 .. _`#1027`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1027
497 .. _`#1028`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1028
498 .. _`#1033`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1033
499 .. _`#1034`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1034
500 .. _`#1037`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1037
501 .. _`#1054`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1054
502 .. _`#1062`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1062
503 .. _`#1066`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1066
504 .. _`#1068`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1068
505 .. _`#1076`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1076
506 .. _`#1082`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1082
507 .. _architecture.rst: docs/architecture.rst
508 .. _FTP-and-SFTP.rst: docs/frontends/FTP-and-SFTP.rst
510 Release 1.6.1 (2010-02-27)
511 --------------------------
516 - Correct handling of Small Immutable Directories
518 Immutable directories can now be deep-checked and listed in the web
519 UI in all cases. (In v1.6.0, some operations, such as deep-check, on
520 a directory graph that included very small immutable directories,
521 would result in an exception causing the whole operation to abort.)
524 Usability Improvements
525 ''''''''''''''''''''''
527 - Improved user interface messages and error reporting. (`#681`_,
529 - The timeouts for operation handles have been greatly increased, so
530 that you can view the results of an operation up to 4 days after it
531 has completed. After viewing them for the first time, the results
532 are retained for a further day. (`#577`_)
534 Release 1.6.0 (2010-02-01)
535 --------------------------
540 - Immutable Directories
542 Tahoe-LAFS can now create and handle immutable
543 directories. (`#607`_, `#833`_, `#931`_) These are read just like
544 normal directories, but are "deep-immutable", meaning that all their
545 children (and everything reachable from those children) must be
546 immutable objects (i.e. immutable or literal files, and other
547 immutable directories).
549 These directories must be created in a single webapi call that
550 provides all of the children at once. (Since they cannot be changed
551 after creation, the usual create/add/add sequence cannot be used.)
552 They have URIs that start with "URI:DIR2-CHK:" or "URI:DIR2-LIT:",
553 and are described on the human-facing web interface (aka the "WUI")
554 with a "DIR-IMM" abbreviation (as opposed to "DIR" for the usual
555 read-write directories and "DIR-RO" for read-only directories).
557 Tahoe-LAFS releases before 1.6.0 cannot read the contents of an
558 immutable directory. 1.5.0 will tolerate their presence in a
559 directory listing (and display it as "unknown"). 1.4.1 and earlier
560 cannot tolerate them: a DIR-IMM child in any directory will prevent
561 the listing of that directory.
563 Immutable directories are repairable, just like normal immutable
566 The webapi "POST t=mkdir-immutable" call is used to create immutable
567 directories. See `webapi.rst`_ for details.
569 - "tahoe backup" now creates immutable directories, backupdb has
572 The "tahoe backup" command has been enhanced to create immutable
573 directories (in previous releases, it created read-only mutable
574 directories) (`#828`_). This is significantly faster, since it does
575 not need to create an RSA keypair for each new directory. Also
576 "DIR-IMM" immutable directories are repairable, unlike "DIR-RO"
577 read-only mutable directories at present. (A future Tahoe-LAFS
578 release should also be able to repair DIR-RO.)
580 In addition, the backupdb (used by "tahoe backup" to remember what
581 it has already copied) has been enhanced to store information about
582 existing immutable directories. This allows it to re-use directories
583 that have moved but still contain identical contents, or that have
584 been deleted and later replaced. (The 1.5.0 "tahoe backup" command
585 could only re-use directories that were in the same place as they
586 were in the immediately previous backup.) With this change, the
587 backup process no longer needs to read the previous snapshot out of
588 the Tahoe-LAFS grid, reducing the network load
589 considerably. (`#606`_)
591 A "null backup" (in which nothing has changed since the previous
592 backup) will require only two Tahoe-side operations: one to add an
593 Archives/$TIMESTAMP entry, and a second to update the Latest/
594 link. On the local disk side, it will readdir() all your local
595 directories and stat() all your local files.
597 If you've been using "tahoe backup" for a while, you will notice
598 that your first use of it after upgrading to 1.6.0 may take a long
599 time: it must create proper immutable versions of all the old
600 read-only mutable directories. This process won't take as long as
601 the initial backup (where all the file contents had to be uploaded
602 too): it will require time proportional to the number and size of
603 your directories. After this initial pass, all subsequent passes
604 should take a tiny fraction of the time.
606 As noted above, Tahoe-LAFS versions earlier than 1.5.0 cannot list a
607 directory containing an immutable subdirectory. Tahoe-LAFS versions
608 earlier than 1.6.0 cannot read the contents of an immutable
611 The "tahoe backup" command has been improved to skip over unreadable
612 objects (like device files, named pipes, and files with permissions
613 that prevent the command from reading their contents), instead of
614 throwing an exception and terminating the backup process. It also
615 skips over symlinks, because these cannot be represented faithfully
616 in the Tahoe-side filesystem. A warning message will be emitted each
617 time something is skipped. (`#729`_, `#850`_, `#641`_)
619 - "create-node" command added, "create-client" now implies
622 The basic idea behind Tahoe-LAFS's client+server and client-only
623 processes is that you are creating a general-purpose Tahoe-LAFS
624 "node" process, which has several components that can be
625 activated. Storage service is one of these optional components, as
626 is the Helper, FTP server, and SFTP server. Web gateway
627 functionality is nominally on this list, but it is always active; a
628 future release will make it optional. There are three special
629 purpose servers that can't currently be run as a component in a
630 node: introducer, key-generator, and stats-gatherer.
632 So now "tahoe create-node" will create a Tahoe-LAFS node process,
633 and after creation you can edit its tahoe.cfg to enable or disable
634 the desired services. It is a more general-purpose replacement for
635 "tahoe create-client". The default configuration has storage
636 service enabled. For convenience, the "--no-storage" argument makes
637 a tahoe.cfg file that disables storage service. (`#760`_)
639 "tahoe create-client" has been changed to create a Tahoe-LAFS node
640 without a storage service. It is equivalent to "tahoe create-node
641 --no-storage". This helps to reduce the confusion surrounding the
642 use of a command with "client" in its name to create a storage
643 *server*. Use "tahoe create-client" to create a purely client-side
644 node. If you want to offer storage to the grid, use "tahoe
645 create-node" instead.
647 In the future, other services will be added to the node, and they
648 will be controlled through options in tahoe.cfg . The most important
649 of these services may get additional --enable-XYZ or --disable-XYZ
650 arguments to "tahoe create-node".
652 - Performance Improvements
654 Download of immutable files begins as soon as the downloader has
655 located the K necessary shares (`#928`_, `#287`_). In both the
656 previous and current releases, a downloader will first issue queries
657 to all storage servers on the grid to locate shares before it begins
658 downloading the shares. In previous releases of Tahoe-LAFS, download
659 would not begin until all storage servers on the grid had replied to
660 the query, at which point K shares would be chosen for download from
661 among the shares that were located. In this release, download begins
662 as soon as any K shares are located. This means that downloads start
663 sooner, which is particularly important if there is a server on the
664 grid that is extremely slow or even hung in such a way that it will
665 never respond. In previous releases such a server would have a
666 negative impact on all downloads from that grid. In this release,
667 such a server will have no impact on downloads, as long as K shares
668 can be found on other, quicker, servers. This also means that
669 downloads now use the "best-alacrity" servers that they talk to, as
670 measured by how quickly the servers reply to the initial query. This
671 might cause downloads to go faster, especially on grids with
672 heterogeneous servers or geographical dispersion.
677 - The webapi acquired a new "t=mkdir-with-children" command, to create
678 and populate a directory in a single call. This is significantly
679 faster than using separate "t=mkdir" and "t=set-children" operations
680 (it uses one gateway-to-grid roundtrip, instead of three or
683 - The t=set-children (note the hyphen) operation is now documented in
684 webapi.rst, and is the new preferred spelling of the
685 old t=set_children (with an underscore). The underscore version
686 remains for backwards compatibility. (`#381`_, `#927`_)
688 - The tracebacks produced by errors in CLI tools should now be in
689 plain text, instead of HTML (which is unreadable outside of a
692 - The [storage]reserved_space configuration knob (which causes the
693 storage server to refuse shares when available disk space drops
694 below a threshold) should work on Windows now, not just
697 - "tahoe cp" should now exit with status "1" if it cannot figure out a
698 suitable target filename, such as when you copy from a bare
701 - "tahoe get" no longer creates a zero-length file upon
704 - "tahoe ls" can now list single files. (`#457`_)
706 - "tahoe deep-check --repair" should tolerate repair failures now,
707 instead of halting traversal. (`#874`_, `#786`_)
709 - "tahoe create-alias" no longer corrupts the aliases file if it had
710 previously been edited to have no trailing newline. (`#741`_)
712 - Many small packaging improvements were made to facilitate the
713 "tahoe-lafs" package being included in Ubuntu. Several mac/win32
714 binary libraries were removed, some figleaf code-coverage files were
715 removed, a bundled copy of darcsver-1.2.1 was removed, and
716 additional licensing text was added.
718 - Several DeprecationWarnings for python2.6 were silenced. (`#859`_)
720 - The checker --add-lease option would sometimes fail for shares
721 stored on old (Tahoe v1.2.0) servers. (`#875`_)
723 - The documentation for installing on Windows (docs/quickstart.rst)
724 has been improved. (`#773`_)
726 For other changes not mentioned here, see
727 <https://tahoe-lafs.org/trac/tahoe-lafs/query?milestone=1.6.0&keywords=!~news-done>.
728 To include the tickets mentioned above, go to
729 <https://tahoe-lafs.org/trac/tahoe-lafs/query?milestone=1.6.0>.
731 .. _`#121`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/121
732 .. _`#287`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/287
733 .. _`#381`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/381
734 .. _`#457`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/457
735 .. _`#533`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/533
736 .. _`#577`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/577
737 .. _`#606`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/606
738 .. _`#607`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/607
739 .. _`#637`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/637
740 .. _`#641`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/641
741 .. _`#646`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/646
742 .. _`#681`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/681
743 .. _`#729`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/729
744 .. _`#741`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/741
745 .. _`#760`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/760
746 .. _`#761`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/761
747 .. _`#768`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/768
748 .. _`#773`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/773
749 .. _`#786`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/786
750 .. _`#828`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/828
751 .. _`#833`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/833
752 .. _`#859`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/859
753 .. _`#874`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/874
754 .. _`#875`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/875
755 .. _`#931`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/931
756 .. _`#837`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/837
757 .. _`#850`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/850
758 .. _`#927`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/927
759 .. _`#928`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/928
760 .. _`#939`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/939
761 .. _`#948`: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/948
762 .. _webapi.rst: docs/frontends/webapi.rst
764 Release 1.5.0 (2009-08-01)
765 --------------------------
770 - Uploads of immutable files now use pipelined writes, improving
771 upload speed slightly (10%) over high-latency connections. (`#392`_)
773 - Processing large directories has been sped up, by removing a O(N^2)
774 algorithm from the dirnode decoding path and retaining unmodified
775 encrypted entries. (`#750`_, `#752`_)
777 - The human-facing web interface (aka the "WUI") received a
778 significant CSS makeover by Kevin Reid, making it much prettier and
779 easier to read. The WUI "check" and "deep-check" forms now include a
780 "Renew Lease" checkbox, mirroring the CLI --add-lease option, so
781 leases can be added or renewed from the web interface.
783 - The CLI "tahoe mv" command now refuses to overwrite
784 directories. (`#705`_)
786 - The CLI "tahoe webopen" command, when run without arguments, will
787 now bring up the "Welcome Page" (node status and mkdir/upload
790 - The 3.5MB limit on mutable files was removed, so it should be
791 possible to upload arbitrarily-sized mutable files. Note, however,
792 that the data format and algorithm remains the same, so using
793 mutable files still requires bandwidth, computation, and RAM in
794 proportion to the size of the mutable file. (`#694`_)
796 - This version of Tahoe-LAFS will tolerate directory entries that
797 contain filecap formats which it does not recognize: files and
798 directories from the future. This should improve the user
799 experience (for 1.5.0 users) when we add new cap formats in the
800 future. Previous versions would fail badly, preventing the user from
801 seeing or editing anything else in those directories. These
802 unrecognized objects can be renamed and deleted, but obviously not
803 read or written. Also they cannot generally be copied. (`#683`_)
808 - deep-check-and-repair now tolerates read-only directories, such as
809 the ones produced by the "tahoe backup" CLI command. Read-only
810 directories and mutable files are checked, but not
811 repaired. Previous versions threw an exception when attempting the
812 repair and failed to process the remaining contents. We cannot yet
813 repair these read-only objects, but at least this version allows the
814 rest of the check+repair to proceed. (`#625`_)
816 - A bug in 1.4.1 which caused a server to be listed multiple times
817 (and frequently broke all connections to that server) was
820 - The plaintext-hashing code was removed from the Helper interface,
821 removing the Helper's ability to mount a
822 partial-information-guessing attack. (`#722`_)
824 Platform/packaging changes
825 ''''''''''''''''''''''''''
827 - Tahoe-LAFS now runs on NetBSD, OpenBSD, ArchLinux, and NixOS, and on
828 an embedded system based on an ARM CPU running at 266 MHz.
830 - Unit test timeouts have been raised to allow the tests to complete
831 on extremely slow platforms like embedded ARM-based NAS boxes, which
832 may take several hours to run the test suite. An ARM-specific
833 data-corrupting bug in an older version of Crypto++ (5.5.2) was
834 identified: ARM-users are encouraged to use recent
835 Crypto++/pycryptopp which avoids this problem.
837 - Tahoe-LAFS now requires a SQLite library, either the sqlite3 that
838 comes built-in with python2.5/2.6, or the add-on pysqlite2 if you're
839 using python2.4. In the previous release, this was only needed for
840 the "tahoe backup" command: now it is mandatory.
842 - Several minor documentation updates were made.
844 - To help get Tahoe-LAFS into Linux distributions like Fedora and
845 Debian, packaging improvements are being made in both Tahoe-LAFS and
846 related libraries like pycryptopp and zfec.
848 - The Crypto++ library included in the pycryptopp package has been
849 upgraded to version 5.6.0 of Crypto++, which includes a more
850 efficient implementation of SHA-256 in assembly for x86 or amd64
857 - no python-2.4.0 or 2.4.1 (2.4.2 is good) (they contained a bug in base64.b32decode)
858 - avoid python-2.6 on windows with mingw: compiler issues
859 - python2.4 requires pysqlite2 (2.5,2.6 does not)
863 .. _#392: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/392
864 .. _#625: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/625
865 .. _#653: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/653
866 .. _#683: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/683
867 .. _#694: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/694
868 .. _#705: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/705
869 .. _#722: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/722
870 .. _#750: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/750
871 .. _#752: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/752
873 Release 1.4.1 (2009-04-13)
874 --------------------------
879 - The big feature for this release is the implementation of garbage
880 collection, allowing Tahoe storage servers to delete shares for old
881 deleted files. When enabled, this uses a "mark and sweep" process:
882 clients are responsible for updating the leases on their shares
883 (generally by running "tahoe deep-check --add-lease"), and servers
884 are allowed to delete any share which does not have an up-to-date
885 lease. The process is described in detail in
886 `garbage-collection.rst`_.
888 The server must be configured to enable garbage-collection, by
889 adding directives to the [storage] section that define an age limit
890 for shares. The default configuration will not delete any shares.
892 Both servers and clients should be upgraded to this release to make
893 the garbage-collection as pleasant as possible. 1.2.0 servers have
894 code to perform the update-lease operation but it suffers from a
895 fatal bug, while 1.3.0 servers have update-lease but will return an
896 exception for unknown storage indices, causing clients to emit an
897 Incident for each exception, slowing the add-lease process down to a
898 crawl. 1.1.0 servers did not have the add-lease operation at all.
900 Security/Usability Problems Fixed
901 '''''''''''''''''''''''''''''''''
903 - A super-linear algorithm in the Merkle Tree code was fixed, which
904 previously caused e.g. download of a 10GB file to take several hours
905 before the first byte of plaintext could be produced. The new
906 "alacrity" is about 2 minutes. A future release should reduce this
907 to a few seconds by fixing ticket `#442`_.
909 - The previous version permitted a small timing attack (due to our use
910 of strcmp) against the write-enabler and lease-renewal/cancel
911 secrets. An attacker who could measure response-time variations of
912 approximatly 3ns against a very noisy background time of about 15ms
913 might be able to guess these secrets. We do not believe this attack
914 was actually feasible. This release closes the attack by first
915 hashing the two strings to be compared with a random secret.
920 - In most cases, HTML tracebacks will only be sent if an "Accept:
921 text/html" header was provided with the HTTP request. This will
922 generally cause browsers to get an HTMLized traceback but send
923 regular text/plain tracebacks to non-browsers (like the CLI
924 clients). More errors have been mapped to useful HTTP error codes.
926 - The streaming webapi operations (deep-check and manifest) now have a
927 way to indicate errors (an output line that starts with "ERROR"
928 instead of being legal JSON). See `webapi.rst`_ for
931 - The storage server now has its own status page (at /storage), linked
932 from the Welcome page. This page shows progress and results of the
933 two new share-crawlers: one which merely counts shares (to give an
934 estimate of how many files/directories are being stored in the
935 grid), the other examines leases and reports how much space would be
936 freed if GC were enabled. The page also shows how much disk space is
937 present, used, reserved, and available for the Tahoe server, and
938 whether the server is currently running in "read-write" mode or
941 - When a directory node cannot be read (perhaps because of insufficent
942 shares), a minimal webapi page is created so that the "more-info"
943 links (including a Check/Repair operation) will still be accessible.
945 - A new "reliability" page was added, with the beginnings of work on a
946 statistical loss model. You can tell this page how many servers you
947 are using and their independent failure probabilities, and it will
948 tell you the likelihood that an arbitrary file will survive each
949 repair period. The "numpy" package must be installed to access this
950 page. A partial paper, written by Shawn Willden, has been added to
951 docs/proposed/lossmodel.lyx .
956 - "tahoe check" and "tahoe deep-check" now accept an "--add-lease"
957 argument, to update a lease on all shares. This is the "mark" side
958 of garbage collection.
960 - In many cases, CLI error messages have been improved: the ugly
961 HTMLized traceback has been replaced by a normal python traceback.
963 - "tahoe deep-check" and "tahoe manifest" now have better error
964 reporting. "tahoe cp" is now non-verbose by default.
966 - "tahoe backup" now accepts several "--exclude" arguments, to ignore
967 certain files (like editor temporary files and version-control
968 metadata) during backup.
970 - On windows, the CLI now accepts local paths like "c:\dir\file.txt",
971 which previously was interpreted as a Tahoe path using a "c:" alias.
973 - The "tahoe restart" command now uses "--force" by default (meaning
974 it will start a node even if it didn't look like there was one
977 - The "tahoe debug consolidate" command was added. This takes a series
978 of independent timestamped snapshot directories (such as those
979 created by the allmydata.com windows backup program, or a series of
980 "tahoe cp -r" commands) and creates new snapshots that used shared
981 read-only directories whenever possible (like the output of "tahoe
982 backup"). In the most common case (when the snapshots are fairly
983 similar), the result will use significantly fewer directories than
984 the original, allowing "deep-check" and similar tools to run much
985 faster. In some cases, the speedup can be an order of magnitude or
986 more. This tool is still somewhat experimental, and only needs to
987 be run on large backups produced by something other than "tahoe
988 backup", so it was placed under the "debug" category.
990 - "tahoe cp -r --caps-only tahoe:dir localdir" is a diagnostic tool
991 which, instead of copying the full contents of files into the local
992 directory, merely copies their filecaps. This can be used to verify
993 the results of a "consolidation" operation.
998 - The codebase no longer rauses RuntimeError as a kind of
999 assert(). Specific exception classes were created for each previous
1000 instance of RuntimeError.
1002 -Many unit tests were changed to use a non-network test harness,
1003 speeding them up considerably.
1005 - Deep-traversal operations (manifest and deep-check) now walk
1006 individual directories in alphabetical order. Occasional turn breaks
1007 are inserted to prevent a stack overflow when traversing directories
1008 with hundreds of entries.
1010 - The experimental SFTP server had its path-handling logic changed
1011 slightly, to accomodate more SFTP clients, although there are still
1014 .. _#442: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/442
1015 .. _#645: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/645
1016 .. _garbage-collection.rst: docs/garbage-collection.rst
1018 Release 1.3.0 (2009-02-13)
1019 --------------------------
1021 Checker/Verifier/Repairer
1022 '''''''''''''''''''''''''
1024 - The primary focus of this release has been writing a checker /
1025 verifier / repairer for files and directories. "Checking" is the
1026 act of asking storage servers whether they have a share for the
1027 given file or directory: if there are not enough shares available,
1028 the file or directory will be unrecoverable. "Verifying" is the act
1029 of downloading and cryptographically asserting that the server's
1030 share is undamaged: it requires more work (bandwidth and CPU) than
1031 checking, but can catch problems that simple checking
1032 cannot. "Repair" is the act of replacing missing or damaged shares
1035 - This release includes a full checker, a partial verifier, and a
1036 partial repairer. The repairer is able to handle missing shares: new
1037 shares are generated and uploaded to make up for the missing
1038 ones. This is currently the best application of the repairer: to
1039 replace shares that were lost because of server departure or
1040 permanent drive failure.
1042 - The repairer in this release is somewhat able to handle corrupted
1043 shares. The limitations are:
1045 - Immutable verifier is incomplete: not all shares are used, and not
1046 all fields of those shares are verified. Therefore the immutable
1047 verifier has only a moderate chance of detecting corrupted shares.
1048 - The mutable verifier is mostly complete: all shares are examined,
1049 and most fields of the shares are validated.
1050 - The storage server protocol offers no way for the repairer to
1051 replace or delete immutable shares. If corruption is detected, the
1052 repairer will upload replacement shares to other servers, but the
1053 corrupted shares will be left in place.
1054 - read-only directories and read-only mutable files must be repaired
1055 by someone who holds the write-cap: the read-cap is
1056 insufficient. Moreover, the deep-check-and-repair operation will
1057 halt with an error if it attempts to repair one of these read-only
1059 - Some forms of corruption can cause both download and repair
1060 operations to fail. A future release will fix this, since download
1061 should be tolerant of any corruption as long as there are at least
1062 'k' valid shares, and repair should be able to fix any file that is
1065 - If the downloader, verifier, or repairer detects share corruption,
1066 the servers which provided the bad shares will be notified (via a
1067 file placed in the BASEDIR/storage/corruption-advisories directory)
1068 so their operators can manually delete the corrupted shares and
1069 investigate the problem. In addition, the "incident gatherer"
1070 mechanism will automatically report share corruption to an incident
1071 gatherer service, if one is configured. Note that corrupted shares
1072 indicate hardware failures, serious software bugs, or malice on the
1073 part of the storage server operator, so a corrupted share should be
1074 considered highly unusual.
1076 - By periodically checking/repairing all files and directories,
1077 objects in the Tahoe filesystem remain resistant to recoverability
1078 failures due to missing and/or broken servers.
1080 - This release includes a wapi mechanism to initiate checks on
1081 individual files and directories (with or without verification, and
1082 with or without automatic repair). A related mechanism is used to
1083 initiate a "deep-check" on a directory: recursively traversing the
1084 directory and its children, checking (and/or verifying/repairing)
1085 everything underneath. Both mechanisms can be run with an
1086 "output=JSON" argument, to obtain machine-readable check/repair
1087 status results. These results include a copy of the filesystem
1088 statistics from the "deep-stats" operation (including total number
1089 of files, size histogram, etc). If repair is possible, a "Repair"
1090 button will appear on the results page.
1092 - The client web interface now features some extra buttons to initiate
1093 check and deep-check operations. When these operations finish, they
1094 display a results page that summarizes any problems that were
1095 encountered. All long-running deep-traversal operations, including
1096 deep-check, use a start-and-poll mechanism, to avoid depending upon
1097 a single long-lived HTTP connection. `webapi.rst`_ has
1103 - The "tahoe backup" command is new in this release, which creates
1104 efficient versioned backups of a local directory. Given a local
1105 pathname and a target Tahoe directory, this will create a read-only
1106 snapshot of the local directory in $target/Archives/$timestamp. It
1107 will also create $target/Latest, which is a reference to the latest
1108 such snapshot. Each time you run "tahoe backup" with the same source
1109 and target, a new $timestamp snapshot will be added. These snapshots
1110 will share directories that have not changed since the last backup,
1111 to speed up the process and minimize storage requirements. In
1112 addition, a small database is used to keep track of which local
1113 files have been uploaded already, to avoid uploading them a second
1114 time. This drastically reduces the work needed to do a "null backup"
1115 (when nothing has changed locally), making "tahoe backup' suitable
1116 to run from a daily cronjob.
1118 Note that the "tahoe backup" CLI command must be used in conjunction
1119 with a 1.3.0-or-newer Tahoe client node; there was a bug in the
1120 1.2.0 webapi implementation that would prevent the last step (create
1121 $target/Latest) from working.
1126 - The 12GiB (approximate) immutable-file-size limitation is
1127 lifted. This release knows how to handle so-called "v2 immutable
1128 shares", which permit immutable files of up to about 18 EiB (about
1129 3*10^14). These v2 shares are created if the file to be uploaded is
1130 too large to fit into v1 shares. v1 shares are created if the file
1131 is small enough to fit into them, so that files created with
1132 tahoe-1.3.0 can still be read by earlier versions if they are not
1133 too large. Note that storage servers also had to be changed to
1134 support larger files, and this release is the first release in which
1135 they are able to do that. Clients will detect which servers are
1136 capable of supporting large files on upload and will not attempt to
1137 upload shares of a large file to a server which doesn't support it.
1142 - Tahoe now includes experimental FTP and SFTP servers. When
1143 configured with a suitable method to translate username+password
1144 into a root directory cap, it provides simple access to the virtual
1145 filesystem. Remember that FTP is completely unencrypted: passwords,
1146 filenames, and file contents are all sent over the wire in
1147 cleartext, so FTP should only be used on a local (127.0.0.1)
1148 connection. This feature is still in development: there are no unit
1149 tests yet, and behavior with respect to Unicode filenames is
1150 uncertain. Please see `FTP-and-SFTP.rst`_ for
1151 configuration details. (`#512`_, `#531`_)
1156 - This release adds the 'tahoe create-alias' command, which is a
1157 combination of 'tahoe mkdir' and 'tahoe add-alias'. This also allows
1158 you to start using a new tahoe directory without exposing its URI in
1159 the argv list, which is publicly visible (through the process table)
1160 on most unix systems. Thanks to Kevin Reid for bringing this issue
1163 - The single-argument form of "tahoe put" was changed to create an
1164 unlinked file. I.e. "tahoe put bar.txt" will take the contents of a
1165 local "bar.txt" file, upload them to the grid, and print the
1166 resulting read-cap; the file will not be attached to any
1167 directories. This seemed a bit more useful than the previous
1168 behavior (copy stdin, upload to the grid, attach the resulting file
1169 into your default tahoe: alias in a child named 'bar.txt').
1171 - "tahoe put" was also fixed to handle mutable files correctly: "tahoe
1172 put bar.txt URI:SSK:..." will read the contents of the local bar.txt
1173 and use them to replace the contents of the given mutable file.
1175 - The "tahoe webopen" command was modified to accept aliases. This
1176 means "tahoe webopen tahoe:" will cause your web browser to open to
1177 a "wui" page that gives access to the directory associated with the
1178 default "tahoe:" alias. It should also accept leading slashes, like
1179 "tahoe webopen tahoe:/stuff".
1181 - Many esoteric debugging commands were moved down into a "debug"
1184 - tahoe debug dump-cap
1185 - tahoe debug dump-share
1186 - tahoe debug find-shares
1187 - tahoe debug catalog-shares
1188 - tahoe debug corrupt-share
1190 The last command ("tahoe debug corrupt-share") flips a random bit
1191 of the given local sharefile. This is used to test the file
1192 verifying/repairing code, and obviously should not be used on user
1195 The cli might not correctly handle arguments which contain non-ascii
1196 characters in Tahoe v1.3 (although depending on your platform it
1197 might, especially if your platform can be configured to pass such
1198 characters on the command-line in utf-8 encoding). See
1199 https://tahoe-lafs.org/trac/tahoe-lafs/ticket/565 for details.
1204 - The "default webapi port", used when creating a new client node (and
1205 in the getting-started documentation), was changed from 8123 to
1206 3456, to reduce confusion when Tahoe accessed through a Firefox
1207 browser on which the "Torbutton" extension has been installed. Port
1208 8123 is occasionally used as a Tor control port, so Torbutton adds
1209 8123 to Firefox's list of "banned ports" to avoid CSRF attacks
1210 against Tor. Once 8123 is banned, it is difficult to diagnose why
1211 you can no longer reach a Tahoe node, so the Tahoe default was
1212 changed. Note that 3456 is reserved by IANA for the "vat" protocol,
1213 but there are argueably more Torbutton+Tahoe users than vat users
1214 these days. Note that this will only affect newly-created client
1215 nodes. Pre-existing client nodes, created by earlier versions of
1216 tahoe, may still be listening on 8123.
1218 - All deep-traversal operations (start-manifest, start-deep-size,
1219 start-deep-stats, start-deep-check) now use a start-and-poll
1220 approach, instead of using a single (fragile) long-running
1221 synchronous HTTP connection. All these "start-" operations use POST
1222 instead of GET. The old "GET manifest", "GET deep-size", and "POST
1223 deep-check" operations have been removed.
1225 - The new "POST start-manifest" operation, when it finally completes,
1226 results in a table of (path,cap), instead of the list of verifycaps
1227 produced by the old "GET manifest". The table is available in
1228 several formats: use output=html, output=text, or output=json to
1229 choose one. The JSON output also includes stats, and a list of
1230 verifycaps and storage-index strings. The "return_to=" and
1231 "when_done=" arguments have been removed from the t=check and
1232 deep-check operations.
1234 - The top-level status page (/status) now has a machine-readable form,
1235 via "/status/?t=json". This includes information about the
1236 currently-active uploads and downloads, which may be useful for
1237 frontends that wish to display progress information. There is no
1238 easy way to correlate the activities displayed here with recent wapi
1241 - Any files in BASEDIR/public_html/ (configurable) will be served in
1242 response to requests in the /static/ portion of the URL space. This
1243 will simplify the deployment of javascript-based frontends that can
1244 still access wapi calls by conforming to the (regrettable)
1245 "same-origin policy".
1247 - The welcome page now has a "Report Incident" button, which is tied
1248 into the "Incident Gatherer" machinery. If the node is attached to
1249 an incident gatherer (via log_gatherer.furl), then pushing this
1250 button will cause an Incident to be signalled: this means recent log
1251 events are aggregated and sent in a bundle to the gatherer. The user
1252 can push this button after something strange takes place (and they
1253 can provide a short message to go along with it), and the relevant
1254 data will be delivered to a centralized incident-gatherer for later
1255 processing by operations staff.
1257 - The "HEAD" method should now work correctly, in addition to the
1258 usual "GET", "PUT", and "POST" methods. "HEAD" is supposed to return
1259 exactly the same headers as "GET" would, but without any of the
1260 actual response body data. For mutable files, this now does a brief
1261 mapupdate (to figure out the size of the file that would be
1262 returned), without actually retrieving the file's contents.
1264 - The "GET" operation on files can now support the HTTP "Range:"
1265 header, allowing requests for partial content. This allows certain
1266 media players to correctly stream audio and movies out of a Tahoe
1267 grid. The current implementation uses a disk-based cache in
1268 BASEDIR/private/cache/download , which holds the plaintext of the
1269 files being downloaded. Future implementations might not use this
1270 cache. GET for immutable files now returns an ETag header.
1272 - Each file and directory now has a "Show More Info" web page, which
1273 contains much of the information that was crammed into the directory
1274 page before. This includes readonly URIs, storage index strings,
1275 object type, buttons to control checking/verifying/repairing, and
1276 deep-check/deep-stats buttons (for directories). For mutable files,
1277 the "replace contents" upload form has been moved here too. As a
1278 result, the directory page is now much simpler and cleaner, and
1279 several potentially-misleading links (like t=uri) are now gone.
1281 - Slashes are discouraged in Tahoe file/directory names, since they
1282 cause problems when accessing the filesystem through the
1283 wapi. However, there are a couple of accidental ways to generate
1284 such names. This release tries to make it easier to correct such
1285 mistakes by escaping slashes in several places, allowing slashes in
1286 the t=info and t=delete commands, and in the source (but not the
1287 target) of a t=rename command.
1292 - Tahoe's dependencies have been extended to require the
1293 "[secure_connections]" feature from Foolscap, which will cause
1294 pyOpenSSL to be required and/or installed. If OpenSSL and its
1295 development headers are already installed on your system, this can
1296 occur automatically. Tahoe now uses pollreactor (instead of the
1297 default selectreactor) to work around a bug between pyOpenSSL and
1298 the most recent release of Twisted (8.1.0). This bug only affects
1299 unit tests (hang during shutdown), and should not impact regular
1302 - The Tahoe source code tarballs now come in two different forms:
1303 regular and "sumo". The regular tarball contains just Tahoe, nothing
1304 else. When building from the regular tarball, the build process will
1305 download any unmet dependencies from the internet (starting with the
1306 index at PyPI) so it can build and install them. The "sumo" tarball
1307 contains copies of all the libraries that Tahoe requires (foolscap,
1308 twisted, zfec, etc), so using the "sumo" tarball should not require
1309 any internet access during the build process. This can be useful if
1310 you want to build Tahoe while on an airplane, a desert island, or
1311 other bandwidth-limited environments.
1313 - Similarly, tahoe-lafs.org now hosts a "tahoe-deps" tarball which
1314 contains the latest versions of all these dependencies. This
1316 https://tahoe-lafs.org/source/tahoe/deps/tahoe-deps.tar.gz, can be
1317 unpacked in the tahoe source tree (or in its parent directory), and
1318 the build process should satisfy its downloading needs from it
1319 instead of reaching out to PyPI. This can be useful if you want to
1320 build Tahoe from a darcs checkout while on that airplane or desert
1323 - Because of the previous two changes ("sumo" tarballs and the
1324 "tahoe-deps" bundle), most of the files have been removed from
1325 misc/dependencies/ . This brings the regular Tahoe tarball down to
1326 2MB (compressed), and the darcs checkout (without history) to about
1327 7.6MB. A full darcs checkout will still be fairly large (because of
1328 the historical patches which included the dependent libraries), but
1329 a 'lazy' one should now be small.
1331 - The default "make" target is now an alias for "setup.py build",
1332 which itself is an alias for "setup.py develop --prefix support",
1333 with some extra work before and after (see setup.cfg). Most of the
1334 complicated platform-dependent code in the Makefile was rewritten in
1335 Python and moved into setup.py, simplifying things considerably.
1337 - Likewise, the "make test" target now delegates most of its work to
1338 "setup.py test", which takes care of getting PYTHONPATH configured
1339 to access the tahoe code (and dependencies) that gets put in
1340 support/lib/ by the build_tahoe step. This should allow unit tests
1341 to be run even when trial (which is part of Twisted) wasn't already
1342 installed (in this case, trial gets installed to support/bin because
1343 Twisted is a dependency of Tahoe).
1345 - Tahoe is now compatible with the recently-released Python 2.6 ,
1346 although it is recommended to use Tahoe on Python 2.5, on which it
1347 has received more thorough testing and deployment.
1349 - Tahoe is now compatible with simplejson-2.0.x . The previous release
1350 assumed that simplejson.loads always returned unicode strings, which
1351 is no longer the case in 2.0.x .
1353 Grid Management Tools
1354 '''''''''''''''''''''
1356 - Several tools have been added or updated in the misc/ directory,
1357 mostly munin plugins that can be used to monitor a storage grid.
1359 - The misc/spacetime/ directory contains a "disk watcher" daemon
1360 (startable with 'tahoe start'), which can be configured with a set
1361 of HTTP URLs (pointing at the wapi '/statistics' page of a bunch of
1362 storage servers), and will periodically fetch
1363 disk-used/disk-available information from all the servers. It keeps
1364 this information in an Axiom database (a sqlite-based library
1365 available from divmod.org). The daemon computes time-averaged rates
1366 of disk usage, as well as a prediction of how much time is left
1367 before the grid is completely full.
1369 - The misc/munin/ directory contains a new set of munin plugins
1370 (tahoe_diskleft, tahoe_diskusage, tahoe_doomsday) which talk to the
1371 disk-watcher and provide graphs of its calculations.
1373 - To support the disk-watcher, the Tahoe statistics component
1374 (visible through the wapi at the /statistics/ URL) now includes
1375 disk-used and disk-available information. Both are derived through
1376 an equivalent of the unix 'df' command (i.e. they ask the kernel
1377 for the number of free blocks on the partition that encloses the
1378 BASEDIR/storage directory). In the future, the disk-available
1379 number will be further influenced by the local storage policy: if
1380 that policy says that the server should refuse new shares when less
1381 than 5GB is left on the partition, then "disk-available" will
1382 report zero even though the kernel sees 5GB remaining.
1384 - The 'tahoe_overhead' munin plugin interacts with an
1385 allmydata.com-specific server which reports the total of the
1386 'deep-size' reports for all active user accounts, compares this
1387 with the disk-watcher data, to report on overhead percentages. This
1388 provides information on how much space could be recovered once
1389 Tahoe implements some form of garbage collection.
1391 Configuration Changes: single INI-format tahoe.cfg file
1392 '''''''''''''''''''''''''''''''''''''''''''''''''''''''
1394 - The Tahoe node is now configured with a single INI-format file,
1395 named "tahoe.cfg", in the node's base directory. Most of the
1396 previous multiple-separate-files are still read for backwards
1397 compatibility (the embedded SSH debug server and the
1398 advertised_ip_addresses files are the exceptions), but new
1399 directives will only be added to tahoe.cfg . The "tahoe
1400 create-client" command will create a tahoe.cfg for you, with sample
1401 values commented out. (ticket `#518`_)
1403 - tahoe.cfg now has controls for the foolscap "keepalive" and
1404 "disconnect" timeouts (`#521`_).
1406 - tahoe.cfg now has controls for the encoding parameters:
1407 "shares.needed" and "shares.total" in the "[client]" section. The
1408 default parameters are still 3-of-10.
1410 - The inefficient storage 'sizelimit' control (which established an
1411 upper bound on the amount of space that a storage server is allowed
1412 to consume) has been replaced by a lightweight 'reserved_space'
1413 control (which establishes a lower bound on the amount of remaining
1414 space). The storage server will reject all writes that would cause
1415 the remaining disk space (as measured by a '/bin/df' equivalent) to
1416 drop below this value. The "[storage]reserved_space=" tahoe.cfg
1417 parameter controls this setting. (note that this only affects
1418 immutable shares: it is an outstanding bug that reserved_space does
1419 not prevent the allocation of new mutable shares, nor does it
1420 prevent the growth of existing mutable shares).
1425 - Clients now declare which versions of the protocols they
1426 support. This is part of a new backwards-compatibility system:
1427 https://tahoe-lafs.org/trac/tahoe-lafs/wiki/Versioning .
1429 - The version strings for human inspection (as displayed on the
1430 Welcome web page, and included in logs) now includes a platform
1431 identifer (frequently including a linux distribution name, processor
1434 - Several bugs have been fixed, including one that would cause an
1435 exception (in the logs) if a wapi download operation was cancelled
1436 (by closing the TCP connection, or pushing the "stop" button in a
1439 - Tahoe now uses Foolscap "Incidents", writing an "incident report"
1440 file to logs/incidents/ each time something weird occurs. These
1441 reports are available to an "incident gatherer" through the flogtool
1442 command. For more details, please see the Foolscap logging
1443 documentation. An incident-classifying plugin function is provided
1444 in misc/incident-gatherer/classify_tahoe.py .
1446 - If clients detect corruption in shares, they now automatically
1447 report it to the server holding that share, if it is new enough to
1448 accept the report. These reports are written to files in
1449 BASEDIR/storage/corruption-advisories .
1451 - The 'nickname' setting is now defined to be a UTF-8 -encoded string,
1452 allowing non-ascii nicknames.
1454 - The 'tahoe start' command will now accept a --syslog argument and
1455 pass it through to twistd, making it easier to launch non-Tahoe
1456 nodes (like the cpu-watcher) and have them log to syslogd instead of
1457 a local file. This is useful when running a Tahoe node out of a USB
1460 - The Mac GUI in src/allmydata/gui/ has been improved.
1462 .. _#512: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/512
1463 .. _#518: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/518
1464 .. _#521: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/521
1465 .. _#531: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/531
1467 Release 1.2.0 (2008-07-21)
1468 --------------------------
1473 - This release makes the immutable-file "ciphertext hash tree"
1474 mandatory. Previous releases allowed the uploader to decide whether
1475 their file would have an integrity check on the ciphertext or not. A
1476 malicious uploader could use this to create a readcap that would
1477 download as one file or a different one, depending upon which shares
1478 the client fetched first, with no errors raised. There are other
1479 integrity checks on the shares themselves, preventing a storage
1480 server or other party from violating the integrity properties of the
1481 read-cap: this failure was only exploitable by the uploader who
1482 gives you a carefully constructed read-cap. If you download the file
1483 with Tahoe 1.2.0 or later, you will not be vulnerable to this
1486 This change does not introduce a compatibility issue, because all
1487 existing versions of Tahoe will emit the ciphertext hash tree in
1493 - Tahoe now requires Foolscap-0.2.9 . It also requires pycryptopp 0.5
1494 or newer, since earlier versions had a bug that interacted with
1495 specific compiler versions that could sometimes result in incorrect
1496 encryption behavior. Both packages are included in the Tahoe source
1497 tarball in misc/dependencies/ , and should be built automatically
1503 - Web API directory pages should now contain properly-slash-terminated
1504 links to other directories. They have also stopped using absolute
1505 links in forms and pages (which interfered with the use of a
1506 front-end load-balancing proxy).
1508 - The behavior of the "Check This File" button changed, in conjunction
1509 with larger internal changes to file checking/verification. The
1510 button triggers an immediate check as before, but the outcome is
1511 shown on its own page, and does not get stored anywhere. As a
1512 result, the web directory page no longer shows historical checker
1515 - A new "Deep-Check" button has been added, which allows a user to
1516 initiate a recursive check of the given directory and all files and
1517 directories reachable from it. This can cause quite a bit of work,
1518 and has no intermediate progress information or feedback about the
1519 process. In addition, the results of the deep-check are extremely
1520 limited. A later release will improve this behavior.
1522 - The web server's behavior with respect to non-ASCII (unicode)
1523 filenames in the "GET save=true" operation has been improved. To
1524 achieve maximum compatibility with variously buggy web browsers, the
1525 server does not try to figure out the character set of the inbound
1526 filename. It just echoes the same bytes back to the browser in the
1527 Content-Disposition header. This seems to make both IE7 and Firefox
1530 Checker/Verifier/Repairer
1531 '''''''''''''''''''''''''
1533 - Tahoe is slowly acquiring convenient tools to check up on file
1534 health, examine existing shares for errors, and repair files that
1535 are not fully healthy. This release adds a mutable
1536 checker/verifier/repairer, although testing is very limited, and
1537 there are no web interfaces to trigger repair yet. The "Check"
1538 button next to each file or directory on the wapi page will perform
1539 a file check, and the "deep check" button on each directory will
1540 recursively check all files and directories reachable from there
1541 (which may take a very long time).
1543 Future releases will improve access to this functionality.
1545 Operations/Packaging
1546 ''''''''''''''''''''
1548 - A "check-grid" script has been added, along with a Makefile
1549 target. This is intended (with the help of a pre-configured node
1550 directory) to check upon the health of a Tahoe grid, uploading and
1551 downloading a few files. This can be used as a monitoring tool for a
1552 deployed grid, to be run periodically and to signal an error if it
1553 ever fails. It also helps with compatibility testing, to verify that
1554 the latest Tahoe code is still able to handle files created by an
1557 - The munin plugins from misc/munin/ are now copied into any generated
1558 debian packages, and are made executable (and uncompressed) so they
1559 can be symlinked directly from /etc/munin/plugins/ .
1561 - Ubuntu "Hardy" was added as a supported debian platform, with a
1562 Makefile target to produce hardy .deb packages. Some notes have been
1563 added to `debian.rst`_ about building Tahoe on a debian/ubuntu
1566 - Storage servers now measure operation rates and
1567 latency-per-operation, and provides results through the /statistics
1568 web page as well as the stats gatherer. Munin plugins have been
1574 - Tahoe nodes now use Foolscap "incident logging" to record unusual
1575 events to their NODEDIR/logs/incidents/ directory. These incident
1576 files can be examined by Foolscap logging tools, or delivered to an
1577 external log-gatherer for further analysis. Note that Tahoe now
1578 requires Foolscap-0.2.9, since 0.2.8 had a bug that complained about
1579 "OSError: File exists" when trying to create the incidents/
1580 directory for a second time.
1582 - If no servers are available when retrieving a mutable file (like a
1583 directory), the node now reports an error instead of hanging
1584 forever. Earlier releases would not only hang (causing the wapi
1585 directory listing to get stuck half-way through), but the internal
1586 dirnode serialization would cause all subsequent attempts to
1587 retrieve or modify the same directory to hang as well. `#463`_
1589 - A minor internal exception (reported in logs/twistd.log, in the
1590 "stopProducing" method) was fixed, which complained about
1591 "self._paused_at not defined" whenever a file download was stopped
1592 from the web browser end.
1594 .. _#463: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/463
1595 .. _#491: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/491
1596 .. _debian.rst: docs/debian.rst
1598 Release 1.1.0 (2008-06-11)
1599 --------------------------
1601 CLI: new "alias" model
1602 ''''''''''''''''''''''
1604 - The new CLI code uses an scp/rsync -like interface, in which
1605 directories in the Tahoe storage grid are referenced by a
1606 colon-suffixed alias. The new commands look like:
1608 - tahoe cp local.txt tahoe:virtual.txt
1609 - tahoe ls work:subdir
1611 - More functionality is available through the CLI: creating unlinked
1612 files and directories, recursive copy in or out of the storage grid,
1613 hardlinks, and retrieving the raw read- or write- caps through the
1614 'ls' command. Please read `CLI.rst`_ for complete details.
1616 wapi: new pages, new commands
1617 '''''''''''''''''''''''''''''
1619 - Several new pages were added to the web API:
1621 - /helper_status : to describe what a Helper is doing
1622 - /statistics : reports node uptime, CPU usage, other stats
1623 - /file : for easy file-download URLs, see `#221`_
1624 - /cap == /uri : future compatibility
1626 - The localdir=/localfile= and t=download operations were
1627 removed. These required special configuration to enable anyways, but
1628 this feature was a security problem, and was mostly obviated by the
1629 new "cp -r" command.
1631 - Several new options to the GET command were added:
1633 - t=deep-size : add up the size of all immutable files reachable from the directory
1634 - t=deep-stats : return a JSON-encoded description of number of files, size distribution, total size, etc
1636 - POST is now preferred over PUT for most operations which cause
1639 - Most wapi calls now accept overwrite=, and default to overwrite=true
1641 - "POST /uri/DIRCAP/parent/child?t=mkdir" is now the preferred API to
1642 create multiple directories at once, rather than ...?t=mkdir-p .
1644 - PUT to a mutable file ("PUT /uri/MUTABLEFILECAP", "PUT
1645 /uri/DIRCAP/child") will modify the file in-place.
1647 - more munin graphs in misc/munin/
1650 - tahoe-rootdir-space
1651 - tahoe_estimate_files
1652 - mutable files published/retrieved
1661 - setuptools (now required at runtime)
1663 New Mutable-File Code
1664 '''''''''''''''''''''
1666 - The mutable-file handling code (mostly used for directories) has
1667 been completely rewritten. The new scheme has a better API (with a
1668 modify() method) and is less likely to lose data when several
1669 uncoordinated writers change a file at the same time.
1671 - In addition, a single Tahoe process will coordinate its own
1672 writes. If you make two concurrent directory-modifying wapi calls to
1673 a single tahoe node, it will internally make one of them wait for
1674 the other to complete. This prevents auto-collision (`#391`_).
1676 - The new mutable-file code also detects errors during publish
1677 better. Earlier releases might believe that a mutable file was
1678 published when in fact it failed.
1683 - The node now monitors its own CPU usage, as a percentage, measured
1684 every 60 seconds. 1/5/15 minute moving averages are available on the
1685 /statistics web page and via the stats-gathering interface.
1687 - Clients now accelerate reconnection to all servers after being
1688 offline (`#374`_). When a client is offline for a long time, it
1689 scales back reconnection attempts to approximately once per hour, so
1690 it may take a while to make the first attempt, but once any attempt
1691 succeeds, the other server connections will be retried immediately.
1693 - A new "offloaded KeyGenerator" facility can be configured, to move
1694 RSA key generation out from, say, a wapi node, into a separate
1695 process. RSA keys can take several seconds to create, and so a wapi
1696 node which is being used for directory creation will be unavailable
1697 for anything else during this time. The Key Generator process will
1698 pre-compute a small pool of keys, to speed things up further. This
1699 also takes better advantage of multi-core CPUs, or SMP hosts.
1701 - The node will only use a potentially-slow "du -s" command at startup
1702 (to measure how much space has been used) if the "sizelimit"
1703 parameter has been configured (to limit how much space is
1704 used). Large storage servers should turn off sizelimit until a later
1705 release improves the space-management code, since "du -s" on a
1706 terabyte filesystem can take hours.
1708 - The Introducer now allows new announcements to replace old ones, to
1709 avoid buildups of obsolete announcements.
1711 - Immutable files are limited to about 12GiB (when using the default
1712 3-of-10 encoding), because larger files would be corrupted by the
1713 four-byte share-size field on the storage servers (`#439`_). A later
1714 release will remove this limit. Earlier releases would allow >12GiB
1715 uploads, but the resulting file would be unretrievable.
1717 - The docs/ directory has been rearranged, with old docs put in
1718 docs/historical/ and not-yet-implemented ones in docs/proposed/ .
1720 - The Mac OS-X FUSE plugin has a significant bug fix: earlier versions
1721 would corrupt writes that used seek() instead of writing the file in
1722 linear order. The rsync tool is known to perform writes in this
1723 order. This has been fixed.
1725 .. _#221: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/221
1726 .. _#374: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/374
1727 .. _#391: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/391
1728 .. _#439: https://tahoe-lafs.org/trac/tahoe-lafs/ticket/439
1729 .. _CLI.rst: docs/CLI.rst