-ANNOUNCING Allmydata.org "Tahoe", the Least-Authority Filesystem, v1.1
+ANNOUNCING Tahoe, the Least-Authority File Store, v1.10.2
-We are pleased to announce the release of version 1.1 of the "Tahoe"
-Least Authority Filesystem.
+The Tahoe-LAFS team is pleased to announce version 1.10.2 of
+Tahoe-LAFS, an extremely reliable decentralized storage system.
+Get it here:
-The "Tahoe" Least Authority Filesystem 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 it continues to function 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:
-A one-page explanation of the security and fault-tolerance properties
-that it offers is visible at:
+https://tahoe-lafs.org/source/tahoe-lafs/trunk/docs/about.rst
-http://allmydata.org/source/tahoe/trunk/docs/about.html
+The previous stable release of Tahoe-LAFS was v1.10.1, released
+on June 15, 2015.
+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.
-This is the successor to Allmydata.org "Tahoe" Least Authority
-Filesystem v1.0, which was released March 25, 2008 [1]. This release
-fixes several serious issues in Tahoe v1.0, and improves the user
-interfaces. See the known_issues.txt file [2] and the NEWS file [3]
-for details.
+WHAT IS IT GOOD FOR?
-COMPATIBILITY
-
-The version 1 branch of Tahoe is used as the basis of the consumer
-backup product from Allmydata, Inc. -- http://allmydata.com .
-
-Tahoe v1.1 is fully compatible with Tahoe v1.0. v1.1 clients produce
-files which can be read by v1.0 clients. v1.1 clients can read files
-produced by clients of all versions >= v0.8. v1.1 servers can serve
-v1.0 clients and v1.1 clients can use v1.0 servers.
-
-This is the second release in the version 1 series. We believe that
-this version of Tahoe is stable enough to rely on as a permanent store
-of valuable data. The version 1 branch 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.
+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
-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
-cryptographic capability-based 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 the product of less than two years of active
-development, we do not categorically recommend it for the storage of
-data which is extremely confidential or precious. However, we believe
-that the combination of erasure coding, strong encryption, and careful
-engineering makes the use of this software a much safer alternative
-than common alternatives, such as RAID, or traditional backup onto a
-remote server, removable drive, or tape.
-This software comes with extensive unit tests [4], 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 [2].)
+COMPATIBILITY
-This release of Tahoe is suitable for the "friendnet" use case [5] --
-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.
+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" [6]
-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" [7] 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 "docs/install.html" [8].
+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 [9] to discuss uses of Tahoe.
-Patches that extend and improve Tahoe are gratefully accepted -- the
-RoadMap page [10] shows the next improvements that we plan to make and
-CREDITS [11] lists the names of people who've contributed to the
-project. The wiki Dev page [12] 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. [13], 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 instructing them to spend part of
-their work time on this free-software project). We are eternally
-grateful!
+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.
-Zooko O'Whielacronx
-on behalf of the allmydata.org team
-June 11, 2008
+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] http://allmydata.org/trac/tahoe/browser/relnotes.txt?rev=2348
-[2] http://allmydata.org/trac/tahoe/browser/docs/known_issues.txt
-[3] http://allmydata.org/trac/tahoe/browser/docs/NEWS
-[4] http://allmydata.org/trac/tahoe/wiki/Dev
-[5] http://allmydata.org/trac/tahoe/wiki/UseCases
-[6] http://allmydata.org/trac/tahoe/browser/COPYING.GPL
-[7] http://allmydata.org/source/tahoe/trunk/COPYING.TGPPL.html
-[8] http://allmydata.org/source/tahoe/trunk/docs/install.html
-[9] http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev
-[10] http://allmydata.org/trac/tahoe/roadmap
-[11] http://allmydata.org/trac/tahoe/browser/CREDITS?rev=2677
-[12] http://allmydata.org/trac/tahoe/wiki/Dev
-[13] http://allmydata.com
+
+[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
projects / tahoe-lafs / tahoe-lafs.git / blobdiff