ExternalVendorCode/tahoe-lafs
1
0
Fork 0
mirror of https://github.com/tahoe-lafs/tahoe-lafs.git synced 2025-01-18 02:40:07 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

docs: update relnote.txt for Tahoe-LAFS v1.7.0β

Browse Source
This commit is contained in:
Zooko O'Whielacronx 2010-06-08 22:46:02 -07:00
parent 80a89d3931
commit 17733a3e3b
1 changed files with 79 additions and 64 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

143
relnotes.txt
View File

@ -1,52 +1,59 @@
ANNOUNCING Tahoe, the Least-Authority File System, v1.6.1
ANNOUNCING Tahoe, the Least-Authority File System, v1.7.0β
(beta release for Tahoe-LAFS v1.7.0)
(This relnotes.txt document is the beta version of the
relnotes.txt document which will announce Tahoe-LAFS v1.7.0
when it is final.)
The Tahoe-LAFS team is pleased to announce the immediate
availability of version 1.6.1 of Tahoe-LAFS, an extremely
availability of version 1.7.0β of Tahoe-LAFS, an extremely
reliable distributed data store.
Tahoe-LAFS is the first cloud storage system which offers
"provider-independent security" -- meaning that not even your
"provider-independent security"—meaning that not even your
cloud service provider can read or alter your data without
your consent. Here is the one-page explanation of its unique
security and fault-tolerance properties:
http://allmydata.org/source/tahoe/trunk/docs/about.html
http://tahoe-lafs.org/source/tahoe/trunk/docs/about.html
Tahoe-LAFS v1.6.1 is the successor to v1.6.0, which was
released February 2, 2010 [1]. This is a bugfix release which
fixes a few small regressions in v1.6.0.
Tahoe-LAFS v1.7.0β is the successor to v1.6.1, which was released
February 27, 2010 [1].
The v1.6 release includes major performance improvements,
usability improvements, and one major new feature:
deep-immutable directories (cryptographically unalterable
permanent snapshots). See the NEWS file [2] for details.
v1.7.0β is a major new release with new features and a few bugfixes. It
adds a fully functional SFTP interface, support for non-ASCII character
encodings, and a new upload algorithm which guarantees that each file
is spread over multiple servers for fault-tolerance. See the NEWS file
[2] for details.
WHAT IS IT GOOD FOR?
With Tahoe-LAFS, you spread 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
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 and securely share chosen files and
directories with others.
security. You can easily share specific files and directories
with other people.
In addition to the core storage system itself, volunteers have
developed related projects to integrate it with other
tools. These include frontends for Windows, Macintosh,
JavaScript, and iPhone, and plugins for Hadoop, bzr,
duplicity, TiddlyWiki, and more. As of v1.6, contributors have
added an Android frontend and a working read-only FUSE
frontend. See the Related Projects page on the wiki [3].
built other projects on top of Tahoe-LAFS and have integrated
Tahoe-LAFS with existing systems.
We believe that strong encryption, Free/Open Source Software,
erasure coding, and careful engineering practices make
Tahoe-LAFS safer than RAID, removable drive, tape, on-line
backup or other Cloud storage systems.
These related projects include frontends for Windows,
Macintosh, JavaScript, iPhone, and Android, and plugins for
Hadoop, bzr, mercurial, duplicity, TiddlyWiki, and more. See
the Related Projects page on the wiki [3].
We believe that strong encryption, Free and Open Source
Software, erasure coding, and careful engineering practices
make Tahoe-LAFS safer than RAID, removable drive, tape,
on-line backup or other Cloud storage systems.
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 normal
compromise confidentiality or data integrity under recommended
use. (For all currently known issues please see the
known_issues.txt file [4].)
@ -62,17 +69,12 @@ 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.
This is the eigth release in the version 1 series. The version
This is the ninth release in the version 1 series. The version
1 series of Tahoe-LAFS will be actively supported and
maintained for the forseeable future, and future versions of
Tahoe-LAFS will retain the ability to read and write files
compatible with Tahoe-LAFS v1.
In addition, version 1.6 improves forward-compatibility with
planned future directory formats, allowing updates to a
directory containing both current and future links, without
loss of information.
LICENCE
@ -98,7 +100,7 @@ INSTALLATION
Tahoe-LAFS works on Linux, Mac OS X, Windows, Cygwin, Solaris,
*BSD, and probably most other systems. Start with
"docs/install.html" [7].
"docs/quickstart.html" [7].
HACKING AND COMMUNITY
@ -112,42 +114,55 @@ resources for hackers.
SPONSORSHIP
Tahoe-LAFS was originally developed thanks to the sponsorship
of Allmydata, Inc. [12], a provider of commercial backup
services. Allmydata founded the Tahoe-LAFS project and
contributed hardware, software, ideas, bug reports,
suggestions, demands, and they employed several Tahoe-LAFS
hackers and instructed them to spend part of their work time on
this Free Software project. Also they awarded customized
t-shirts to hackers who found security flaws in Tahoe-LAFS (see
the Hack Tahoe-LAFS Hall Of Fame [13]). After discontinuing
funding of Tahoe-LAFS R&D in early 2009, Allmydata, Inc. has
continued to provide servers, co-lo space, bandwidth, and small
personal gifts as tokens of appreciation. (Also they continue
to provide bug reports.) Thank you to Allmydata, Inc. for their
generous and public-spirited support.
Tahoe-LAFS was originally developed by Allmydata, Inc., a
provider of commercial backup services. After discontinuing
funding of Tahoe-LAFS R&D in early 2009, they have continued
to provide servers, bandwidth, small personal gifts as tokens
of appreciation, and bug reports. Thank you to Allmydata,
Inc. for their generous and public-spirited support.
This is the fourth release of Tahoe-LAFS to be created solely
Google, Inc. is sponsoring Tahoe-LAFS development as part of
the Google Summer of Code 2010. Google suggested that we
should apply for the Summer of Code program, and when we did
they generously awarded four sponsorships to students from
around the world to hack on Tahoe-LAFS this summer. Thank you
to Google, Inc. for their generous and public-spirited
support.
HACK TAHOE-LAFS!
If you can find a security flaw in Tahoe-LAFS which is serious
enough that feel compelled to warn our users and issue a fix,
then we will award you with a customized t-shirts with your
exploit printed on it and add you to the "Hack Tahoe-LAFS Hall
Of Fame" [12].
ACKNOWLEDGEMENTS
This is the fifth release of Tahoe-LAFS to be created solely
as a labor of love by volunteers. Thank you very much to the
dedicated team of "hackers in the public interest" who make
Tahoe-LAFS possible.
team of "hackers in the public interest" who make Tahoe-LAFS
possible. In this release we especially owe thanks to
David-Sarah Hopwood, who has dedicated many late nights to the
project and displayed superb software engineering skills.
Zooko Wilcox-O'Hearn
on behalf of the Tahoe-LAFS team
February 27, 2010
June 8, 2010
Boulder, Colorado, USA
[1] http://allmydata.org/trac/tahoe/browser/relnotes.txt?rev=4220
[2] http://allmydata.org/trac/tahoe/browser/NEWS?rev=4243
[3] http://allmydata.org/trac/tahoe/wiki/RelatedProjects
[4] http://allmydata.org/trac/tahoe/browser/docs/known_issues.txt
[5] http://allmydata.org/trac/tahoe/browser/COPYING.GPL
[6] http://allmydata.org/source/tahoe/trunk/COPYING.TGPPL.html
[7] http://allmydata.org/source/tahoe/trunk/docs/install.html
[8] http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev
[9] http://allmydata.org/trac/tahoe/roadmap
[10] http://allmydata.org/trac/tahoe/browser/CREDITS?rev=4243
[11] http://allmydata.org/trac/tahoe/wiki/Dev
[12] http://allmydata.com
[13] http://hacktahoe.org
[1] http://tahoe-lafs.org/trac/tahoe/browser/relnotes.txt?rev=4244
[2] http://tahoe-lafs.org/trac/tahoe/browser/NEWS?rev=4443
[3] http://tahoe-lafs.org/trac/tahoe/wiki/RelatedProjects
[4] http://tahoe-lafs.org/trac/tahoe/browser/docs/known_issues.txt
[5] http://tahoe-lafs.org/trac/tahoe/browser/COPYING.GPL
[6] http://tahoe-lafs.org/source/tahoe/trunk/COPYING.TGPPL.html
[7] http://tahoe-lafs.org/source/tahoe/trunk/docs/quickstart.html
[8] http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
[9] http://tahoe-lafs.org/trac/tahoe/roadmap
[10] http://tahoe-lafs.org/trac/tahoe/browser/CREDITS?rev=4456
[11] http://tahoe-lafs.org/trac/tahoe/wiki/Dev
[12] http://tahoe-lafs.org/hacktahoelafs/