ANN: Tahoe-LAFS 1.11.0 released

Brian Warner warner at
Wed Mar 30 23:57:01 UTC 2016

Hash: SHA1

ANNOUNCING Tahoe, the Least-Authority File Store, v1.11.0

The Tahoe-LAFS team is pleased to announce version 1.11.0 of
Tahoe-LAFS, an extremely reliable decentralized storage system.
Get it here:

in one of the following source files (with their SHA256 hashes):

* tahoe-lafs-1.11.0.tar.bz2
* tahoe-lafs-1.11.0.tar.gz2
* tahoe_lafs-1.11.0-py2-none-any.whl

All files are signed by the Tahoe-LAFS Release-Signing Key, fingerprint
E34E 62D0 6D0E 69CF CA41 79FF BDE0 D31D 6866 6A7A. Look for detached
.asc files next to the tarballs in the directory above, as well as the
pubkey itself in a file named "tahoe-release-signing-gpg-key.asc".

This is git revision 04a3e7993f70ac87c208d61f4387a59f5f419367 on , which is tagged as
"tahoe-lafs-1.11.0" (with a GPG-signed tag, using the same key as

Instructions for download and installation are in:

(but it's just "pip install tahoe-lafs").


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:

The previous stable release of Tahoe-LAFS was v1.10.2, released
on July 30, 2015.

v1.11.0 overhauls the install/packaging system, bringing Tahoe
into line with standard Python practices like "pip",
"virtualenv", and "tox". It can now be installed with "pip
install tahoe-lafs". This release also includes a few small
features, like the "preferred peers" server-selection
configuration, unicode aliases, and welcome-page improvements.
See the NEWS file [1] for details.


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].)


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 twentieth 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.


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
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.)


Tahoe-LAFS works on Linux, Mac OS X, Windows, Solaris, *BSD,
and probably most other systems. Start with "docs/INSTALL.rst"


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.


A special thanks goes out to Least Authority Enterprises [12],
which employs several Tahoe-LAFS developers, for their
continued support.


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].


This is the fifteenth 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

March 30, 2016
San Francisco, California, USA


Version: GnuPG v1


More information about the tahoe-dev mailing list