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