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