ANN: Tahoe-LAFS 1.11.0 released

Thu Mar 31 01:54:34 UTC 2016

To add on to this announcement, I have upgraded the test grid to
v1.11.0. Please let me know if there are any issues, but Brian Warner
was able to answer all my questions during the upgrade process, so I
don't believe I made any mistakes. I can see that 5 nodes have already
connected (including 1 of my own).

On 3/30/2016 7:57 PM, Brian Warner wrote:
> 
> 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:
> 
>   https://tahoe-lafs.org/downloads
> 
> in one of the following source files (with their SHA256 hashes):
> 
> * tahoe-lafs-1.11.0.tar.bz2
>   b1611b0b6dab35f6541b46d03b749b7ee668e0403aa4d9b3bdb5aeacf2413743
> * tahoe-lafs-1.11.0.tar.gz2
>   1552c149f31b5ba0eed58df7bcebc6b3521d92290d0f274bf3c304c51f595d26
> * tahoe-lafs-1.11.0.zip
>   16513e2d3e45dc3751841ffeb00fc71755807c3f5d6710af5d3617081aee664b
> * tahoe_lafs-1.11.0-py2-none-any.whl
>   cee26a2590b84115ebd7d0020c0cc5ecec0b18f726a37183ba09c6dc920f7a70
> 
> 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
> https://github.com/tahoe-lafs/tahoe-lafs.git , which is tagged as
> "tahoe-lafs-1.11.0" (with a GPG-signed tag, using the same key as
> above).
> 
> Instructions for download and installation are in:
> 
>  http://tahoe-lafs.readthedocs.org/en/tahoe-lafs-1.11.0/INSTALL.html
> 
> (but it's just "pip install tahoe-lafs").
> 
> 
> WHAT IS 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:
> 
>   http://tahoe-lafs.readthedocs.org/en/latest/about.html
> 
> 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.
> 
> 
> WHAT IS IT GOOD FOR?
> 
> 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 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.
> 
> 
> 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" [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.)
> 
> 
> INSTALLATION
> 
> Tahoe-LAFS works on Linux, Mac OS X, Windows, Solaris, *BSD,
> and probably most other systems. Start with "docs/INSTALL.rst"
> [6].
> 
> 
> HACKING AND COMMUNITY
> 
> 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
> 
> A special thanks goes out 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 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
> 
> 
> [1] https://github.com/tahoe-lafs/tahoe-lafs/blob/tahoe-lafs-1.11.0/NEWS.rst
> [2]
> https://github.com/tahoe-lafs/tahoe-lafs/blob/master/docs/known_issues.rst
> [3] https://tahoe-lafs.org/trac/tahoe-lafs/wiki/RelatedProjects
> [4]
> https://github.com/tahoe-lafs/tahoe-lafs/blob/tahoe-lafs-1.11.0/COPYING.GPL
> [5]
> https://github.com/tahoe-lafs/tahoe-lafs/blob/tahoe-lafs-1.11.0/COPYING.TGPPL.rst
> [6] http://tahoe-lafs.readthedocs.org/en/tahoe-lafs-1.11.0/INSTALL.html
> [7] https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
> [8] https://tahoe-lafs.org/trac/tahoe-lafs/roadmap
> [9] https://github.com/tahoe-lafs/tahoe-lafs/blob/master/CREDITS
> [10] https://tahoe-lafs.org/trac/tahoe-lafs/wiki/Dev
> [12] https://leastauthority.com/
> [13] https://tahoe-lafs.org/hacktahoelafs/
> [14] http://tahoe-lafs.readthedocs.org/en/tahoe-lafs-1.11.0/nodekeys.html
> 
> 
> _______________________________________________
> tahoe-dev mailing list
> tahoe-dev at tahoe-lafs.org
> https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20160330/7042955d/attachment-0001.sig>