-ANNOUNCING Tahoe, the Least-Authority File System, v1.9.0
+ANNOUNCING Tahoe, the Least-Authority File Store, v1.10.2
-The Tahoe-LAFS team is pleased to announce the immediate
-availability of version 1.9.0 of Tahoe-LAFS, an extremely
-reliable distributed storage system. Get it here:
+The Tahoe-LAFS team is pleased to announce version 1.10.2 of
+Tahoe-LAFS, an extremely reliable decentralized storage system.
+Get it here:
https://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/quickstart.rst
https://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/about.rst
-The previous stable release of Tahoe-LAFS was v1.8.3, which was
-released September 13, 2011.
+The previous stable release of Tahoe-LAFS was v1.10.1, released
+on June 15, 2015.
-v1.9.0 offers a new mutable-file format (more efficient for
-large files), a file-blacklisting feature, and a new
-"drop-upload" feature. See the NEWS file [3] and
-known_issues.rst [4] file for details.
+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-LAFS, you distribute your filesystem across
-multiple servers, and even if some of the servers fail or are
-taken over by an attacker, the entire filesystem continues to
-work correctly, and continues to preserve your privacy and
-security. You can easily share specific files and directories
-with other people.
+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 [5].
+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
COMPATIBILITY
-This release is compatible with the version 1 series of
+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
clients of all versions back to v1.0 and clients from this
release can use servers of all versions back to v1.0.
-This is the fifteenth release in the version 1 series. This
+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
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-shirts with your
+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 ninth 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.
+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
-October 31, 2011
+July 30, 2015
San Francisco, California, USA
-[1] https://tahoe-lafs.org/trac/tahoe-lafs/browser/trunk/NEWS.rst?rev=5356
+[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/source/tahoe/trunk/docs/quickstart.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/trunk/CREDITS?rev=5356
+[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] http://leastauthority.com/
+[12] https://leastauthority.com/
[13] https://tahoe-lafs.org/hacktahoelafs/
+[14] https://tahoe-lafs.org/trac/tahoe-lafs/browser/docs/nodekeys.rst