X-Git-Url: https://git.rkrishnan.org/?a=blobdiff_plain;f=relnotes.txt;h=d7f671b36d08de07f1a0cf0742349962f41b43fd;hb=498563da69dddae86478343c66d437a467274522;hp=fe5c6afdcb431f750418e9a3bddebe86f690ee9b;hpb=bb00e13a11ee7e9ee9224b3c3e9998132e99fc9d;p=tahoe-lafs%2Ftahoe-lafs.git diff --git a/relnotes.txt b/relnotes.txt index fe5c6afd..d7f671b3 100644 --- a/relnotes.txt +++ b/relnotes.txt @@ -1,147 +1,164 @@ -ANNOUNCING Tahoe, the Least-Authority Filesystem, v1.XXX -The allmydata.org team is pleased to announce the release of version -1.XXX of "Tahoe", the Long-lived, Axe-tolerant Filesystem. This is the -second release of Tahoe-LAFS which was created solely as a labor of love -by volunteers -- developer time is no longer funded by allmydata.com (see [1] for -details). +ANNOUNCING Tahoe, the Least-Authority File Store, v1.10.2 -Tahoe-LAFS is a secure, decentralized, fault-tolerant cloud storage -system. All of the source code is publicly available under Free -Software, Open Source licences. +The Tahoe-LAFS team is pleased to announce version 1.10.2 of +Tahoe-LAFS, an extremely reliable decentralized storage system. +Get it here: -This filesystem is distributed over multiple servers in such a way the -filesystem continues to operate correctly even when some of the servers -are unavailable, malfunctioning, or malicious. Here is the one-page -explanation of Tahoe's unique security and fault-tolerance properties: +https://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/quickstart.rst -http://allmydata.org/source/tahoe/trunk/docs/about.html +Tahoe-LAFS is the first distributed storage system to offer +"provider-independent security" — meaning that not even the +operators of your storage servers can read or alter your data +without your consent. Here is the one-page explanation of its +unique security and fault-tolerance properties: -This is the successor to Tahoe-LAFS v1.3, which was released February -13, 2009 [2]. This is a major new release, adding XXX new WUI style, port to ARM CPU and embedded systems such as NAS boxes. +https://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/about.rst -See the NEWS file [3] and the known_issues.txt file [4] for more -information. +The previous stable release of Tahoe-LAFS was v1.10.1, released +on June 15, 2015. -Besides the Tahoe core, a crop of related projects have sprung up, -including frontends for Windows and Macintosh, two front-ends written in -JavaScript, a Ruby interface, a plugin for duplicity, a plugin for -TiddlyWiki, a new backup tool named "GridBackup", CIFS/SMB integration, -an iPhone app, and three incomplete frontends for FUSE. See the Related -Projects page on the wiki: [5]. +v1.10.2 is a small bugfix release, which fixes a critical +packaging error that prevented v1.10.1 from building against the +latest version of the upstream "mock" library. A few small bugs +were fixed too. See the NEWS file [1] for details. -COMPATIBILITY - -Tahoe v1.4 is fully compatible with the version 1 series of Tahoe. Files -written by v1.4 clients can be read by clients of all versions back to -v1.0. v1.4 clients can read files produced by clients of all versions since -v1.0. v1.4 servers can serve clients of all versions back to v1.0 and v1.4 -clients can use servers of all versions back to v1.0. - -This is the fifth release in the version 1 series. The version 1 series -of Tahoe will be actively supported and maintained for the forseeable -future, and future versions of Tahoe will retain the ability to read -files and directories produced by Tahoe v1 for the forseeable future. +WHAT IS IT GOOD FOR? -The version 1 branch of Tahoe is the basis of the consumer backup -product from Allmydata, Inc. -- http://allmydata.com . +With Tahoe-LAFS, you distribute your data across multiple +servers. Even if some of the servers fail or are taken over +by an attacker, the entire file store continues to function +correctly, preserving your privacy and security. You can +easily share specific files and directories with other people. +In addition to the core storage system itself, volunteers +have built other projects on top of Tahoe-LAFS and have +integrated Tahoe-LAFS with existing systems, including +Windows, JavaScript, iPhone, Android, Hadoop, Flume, Django, +Puppet, bzr, mercurial, perforce, duplicity, TiddlyWiki, and +more. See the Related Projects page on the wiki [3]. -WHAT IS IT GOOD FOR? +We believe that strong cryptography, Free and Open Source +Software, erasure coding, and principled engineering practices +make Tahoe-LAFS safer than RAID, removable drive, tape, +on-line backup or cloud storage. -With Tahoe, you can distribute your filesystem across a set of servers, -such that if some of them fail or even turn out to be malicious, the -entire filesystem continues to be available. You can share your files -with other users, using a simple and flexible access control scheme. +This software is developed under test-driven development, and +there are no known bugs or security flaws which would +compromise confidentiality or data integrity under recommended +use. (For all important issues that we are currently aware of +please see the known_issues.rst file [2].) -Because this software is new, we do not categorically recommend it as -the sole repository of data which is extremely confidential or -precious. However, we believe that erasure coding, strong encryption, -Free/Open Source Software and careful engineering make Tahoe safer than -common alternatives, such as RAID, removable drive, tape, "on-line -storage" or "Cloud storage" systems. -This software comes with extensive tests, and there are no known -security flaws which would compromise confidentiality or data integrity. -(For all currently known issues please see the known_issues.txt file -[3].) +COMPATIBILITY -This release of Tahoe is suitable for the "friendnet" use case [6] -- -it is easy to create a filesystem spread over the computers of you and -your friends so that you can share disk space and files. +This release should be compatible with the version 1 series of +Tahoe-LAFS. Clients from this release can write files and +directories in the format used by clients of all versions back +to v1.0 (which was released March 25, 2008). Clients from this +release can read files and directories produced by clients of +all versions since v1.0. Servers from this release can serve +clients of all versions back to v1.0 and clients from this +release can use servers of all versions back to v1.0. + +Except for the new optional MDMF format, we have not made any +intentional compatibility changes. However we do not yet have +the test infrastructure to continuously verify that all new +versions are interoperable with previous versions. We intend +to build such an infrastructure in the future. + +The new Introducer protocol added in v1.10 is backwards +compatible with older clients and introducer servers, however +some features will be unavailable when an older node is +involved. Please see docs/nodekeys.rst [14] for details. + +This is the nineteenth release in the version 1 series. This +series of Tahoe-LAFS will be actively supported and maintained +for the foreseeable future, and future versions of Tahoe-LAFS +will retain the ability to read and write files compatible +with this series. LICENCE -You may use this package under the GNU General Public License, version -2 or, at your option, any later version. See the file "COPYING.GPL" -[7] for the terms of the GNU General Public License, version 2. +You may use this package under the GNU General Public License, +version 2 or, at your option, any later version. See the file +"COPYING.GPL" [4] for the terms of the GNU General Public +License, version 2. -You may use this package under the Transitive Grace Period Public -Licence, version 1 or, at your option, any later version. (The -Transitive Grace Period Public Licence has requirements similar to the -GPL except that it allows you to wait for up to twelve months after you -redistribute a derived work before releasing the source code of your -derived work.) See the file "COPYING.TGPPL.html" [8] for the terms of -the Transitive Grace Period Public Licence, version 1. +You may use this package under the Transitive Grace Period +Public Licence, version 1 or, at your option, any later +version. (The Transitive Grace Period Public Licence has +requirements similar to the GPL except that it allows you to +delay for up to twelve months after you redistribute a derived +work before releasing the source code of your derived work.) +See the file "COPYING.TGPPL.rst" [5] for the terms of the +Transitive Grace Period Public Licence, version 1. -(You may choose to use this package under the terms of either licence, -at your option.) +(You may choose to use this package under the terms of either +licence, at your option.) INSTALLATION -Tahoe works on Linux, Mac OS X, Windows, Cygwin, and Solaris, and -probably most other systems. Start with "docs/install.html" [9]. +Tahoe-LAFS works on Linux, Mac OS X, Windows, Solaris, *BSD, +and probably most other systems. Start with +"docs/quickstart.rst" [6]. HACKING AND COMMUNITY -Please join us on the mailing list [10]. Patches are gratefully -accepted -- the RoadMap page [11] shows the next improvements that we -plan to make and CREDITS [12] lists the names of people who've -contributed to the project. The wiki Dev page [13] contains resources -for hackers. +Please join us on the mailing list [7]. Patches are gratefully +accepted -- the RoadMap page [8] shows the next improvements +that we plan to make and CREDITS [9] lists the names of people +who've contributed to the project. The Dev page [10] contains +resources for hackers. SPONSORSHIP -Tahoe was originally developed thanks to the sponsorship of Allmydata, -Inc. [14], a provider of commercial backup services. Allmydata, -Inc. created the Tahoe project, and contributed hardware, software, -ideas, bug reports, suggestions, demands, and money (employing several -Tahoe hackers and instructing them to spend part of their work time on -this Free Software project). Also they awarded customized t-shirts to -hackers who find security flaws in Tahoe (see http://hacktahoe.org -). After discontinuing funding of Tahoe R&D in early 2009, Allmydata, -Inc. has continued to provide servers, co-lo space and bandwidth to the -open source project. Thank you to Allmydata, Inc. for their generous and -public-spirited support. - - -Zooko Wilcox-O'Hearn -on behalf of the allmydata.org team - -Special acknowledgment goes to Brian Warner, whose superb engineering -skills and dedication are primarily responsible for the Tahoe -implementation, and significantly responsible for the Tahoe design as -well, not to mention most of the docs and tests and many other things -besides. - -April 13, 2009 -Boulder, Colorado, USA - -[1] http://allmydata.org/pipermail/tahoe-dev/2009-March/001461.html -[2] http://allmydata.org/trac/tahoe/browser/relnotes.txt?rev=3620 -[3] http://allmydata.org/trac/tahoe/browser/NEWS?rev=3835 -[4] http://allmydata.org/trac/tahoe/browser/docs/known_issues.txt -[5] http://allmydata.org/trac/tahoe/wiki/RelatedProjects -[6] http://allmydata.org/trac/tahoe/wiki/UseCases -[7] http://allmydata.org/trac/tahoe/browser/COPYING.GPL -[8] http://allmydata.org/source/tahoe/trunk/COPYING.TGPPL.html -[9] http://allmydata.org/source/tahoe/trunk/docs/install.html -[10] http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev -[11] http://allmydata.org/trac/tahoe/roadmap -[12] http://allmydata.org/trac/tahoe/browser/CREDITS?rev=3758 -[13] http://allmydata.org/trac/tahoe/wiki/Dev -[14] http://allmydata.com +Atlas Networks has contributed several hosted servers for +performance testing. Thank you to Atlas Networks [11] for +their generous and public-spirited support. + +And a special thanks to Least Authority Enterprises [12], +which employs several Tahoe-LAFS developers, for their +continued support. + +HACK TAHOE-LAFS! + +If you can find a security flaw in Tahoe-LAFS which is serious +enough that we feel compelled to warn our users and issue a fix, +then we will award you with a customized t-shirt with your +exploit printed on it and add you to the "Hack Tahoe-LAFS Hall +Of Fame" [13]. + + +ACKNOWLEDGEMENTS + +This is the fourteenth release of Tahoe-LAFS to be created +solely as a labor of love by volunteers. Thank you very much +to the team of "hackers in the public interest" who make +Tahoe-LAFS possible. + +Brian Warner +on behalf of the Tahoe-LAFS team + +July 30, 2015 +San Francisco, California, USA + + +[1] https://tahoe-lafs.org/trac/tahoe-lafs/browser/NEWS.rst +[2] https://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/known_issues.rst +[3] https://tahoe-lafs.org/trac/tahoe-lafs/wiki/RelatedProjects +[4] https://tahoe-lafs.org/trac/tahoe-lafs/browser/COPYING.GPL +[5] https://tahoe-lafs.org/trac/tahoe-lafs/browser/COPYING.TGPPL.rst +[6] https://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/quickstart.rst +[7] https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev +[8] https://tahoe-lafs.org/trac/tahoe-lafs/roadmap +[9] https://tahoe-lafs.org/trac/tahoe-lafs/browser/CREDITS +[10] https://tahoe-lafs.org/trac/tahoe-lafs/wiki/Dev +[11] http://atlasnetworks.us/ +[12] https://leastauthority.com/ +[13] https://tahoe-lafs.org/hacktahoelafs/ +[14] https://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/nodekeys.rst