X-Git-Url: https://git.rkrishnan.org/?a=blobdiff_plain;f=relnotes.txt;h=d7f671b36d08de07f1a0cf0742349962f41b43fd;hb=HEAD;hp=f6f1e30b9597e55c59365e4c6f3c05c0d6a302f1;hpb=9033d887a31b2f1165a7a515799da4ac5a6a76af;p=tahoe-lafs%2Ftahoe-lafs.git diff --git a/relnotes.txt b/relnotes.txt index f6f1e30b..d7f671b3 100644 --- a/relnotes.txt +++ b/relnotes.txt @@ -1,113 +1,164 @@ -ANNOUNCING: Allmydata-Tahoe version 0.7 +ANNOUNCING Tahoe, the Least-Authority File Store, v1.10.2 -We are pleased to announce the release of version 0.7 of allmydata.org -"Tahoe". +The Tahoe-LAFS team is pleased to announce version 1.10.2 of +Tahoe-LAFS, an extremely reliable decentralized storage system. +Get it here: -Tahoe is a secure, decentralized, fault-tolerant filesystem. All of -the source code is available under a Free Software, Open Source -licence (or two). +https://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/quickstart.rst -This filesystem is encrypted and distributed over multiple peers in -such a way that it continues to work correctlly even when some of the -peers are unavailable, malfunctioning, or malicious. +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 Allmydata-Tahoe v0.6.1, which was released -October 15, 2007 [1]. +https://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/about.rst -This release adds decentralized, encrypted directories and mutable -files, making it the first release of Tahoe in which no part of the -filesystem is centralized. It also adds a FUSE interface, allowing -you to access a distributed Tahoe grid as if it were a normal local -filesystem. +The previous stable release of Tahoe-LAFS was v1.10.1, released +on June 15, 2015. -This is also the first release to be offered under a novel open source -licence which allows people to redistributed proprietary derivatives -of Tahoe for a limited time. +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. WHAT IS IT GOOD FOR? -With Tahoe, you can distribute your filesystem across a set of -computers, such that if some of the computers fail or turn out to be -malicious, the filesystem continues to work from the remaining -computers. You can also share your files with other users, using a -strongly encrypted, capability-based access control scheme. - -This release is targeted at hackers and smart users who are willing to -use a web user interface, a command-line user interface, or a FUSE -interface. (Or a RESTful API. Just telnet to localhost and type HTTP -requests to get started.) - -Because this software is new, it is not yet recommended for storage of -highly confidential data nor for valuable data which is not otherwise -backed up. However, it works well in practice, it comes with extensive -unit tests, and there are no known security flaws which would -compromise confidentiality or data integrity. (For a current -description of all known security issues and an overview of Tahoe's -security properties, please see the Security web page: [2].) - -This release of Tahoe is suitable for the "friendnet" use case [3] -- -it is easy to create a filesystem spread over the computers of you -and your friends so that you can share files and disk space with one -another. +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]. + +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. + +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].) + + +COMPATIBILITY + +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" -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.0. The Transitive Grace Period Public Licence says -that you may distribute proprietary derived works of Tahoe without -releasing the source code of that derived work for up to twelve -months, after which time you are obligated to release the source code -of the derived work under the Transitive Grace Period Public Licence. -See the file "COPYING.TGPPL.html" for the terms of the Transitive -Grace Period Public Licence, version 1.0. +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. For -installation instructions please see "doc/install.html" [4]. +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 [5] to discuss uses of Tahoe. -Patches that extend and improve Tahoe are gratefully accepted -- -roadmap.txt [6] shows the next improvements that we plan to make and -CREDITS [7] lists the names of people who've contributed to the -project. The wiki Dev page [8] 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 is sponsored by Allmydata, Inc. [9], a provider of consumer -backup services. Allmydata, Inc. contributes hardware, software, -ideas, bug reports, suggestions, demands, and money (employing several -allmydata.org Tahoe hackers and allowing them to spend part of their -work time on the next-generation, free-software project). We are -eternally grateful! - - -Zooko O'Whielacronx -on behalf of the allmydata.org team -January 7, 2008 -San Francisco, California - - -[1] http://allmydata.org/trac/tahoe/browser/relnotes.txt?rev=1346 -[2] http://allmydata.org/trac/tahoe/wiki/Security -[3] http://allmydata.org/trac/tahoe/wiki/UseCases -[4] http://allmydata.org/source/tahoe/trunk/docs/install.html -[5] http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev -[6] http://allmydata.org/trac/tahoe/browser/roadmap.txt -[7] http://allmydata.org/trac/tahoe/browser/CREDITS?rev=1424 -[8] http://allmydata.org/trac/tahoe/wiki/Dev -[9] 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