Difference between revisions of "Tahoe-LAFS"

From the Linux and Unix Users Group at Virginia Teck Wiki
Jump to: navigation, search
imported>Marcusw
(Created page with "Tahoe-LAFS is a distributed filesystem which provides redundancy and security for files. =FAQs= Technical documentation on tahoe can be found at its website. However, for the p...")
 
imported>Marcusw
(What does it do?)
Line 7: Line 7:
 
==What does it do?==
 
==What does it do?==
  
You set up a node with a few hundred gigs of free space. Then, you put files in it. It encrypts them and puts parts of them on 10 of the nodes in such a way as to be able to recover the entire file even if up to 7 of the nodes are unavailable.
+
You set up a node with a few hundred gigs of free space and connect it to the tahoe grid. Then, you put files in it. It encrypts each file and puts part of it on ten of the nodes on the grid in such a way as to be able to recover the entire file even if up to 7 of the nodes are unavailable.
  
 
==But what if I don't want people seeing my files?==
 
==But what if I don't want people seeing my files?==

Revision as of 16:23, 29 September 2011

Tahoe-LAFS is a distributed filesystem which provides redundancy and security for files.

FAQs

Technical documentation on tahoe can be found at its website. However, for the prospective user, here's a simple explanation in Q&A format:

What does it do?

You set up a node with a few hundred gigs of free space and connect it to the tahoe grid. Then, you put files in it. It encrypts each file and puts part of it on ten of the nodes on the grid in such a way as to be able to recover the entire file even if up to 7 of the nodes are unavailable.

But what if I don't want people seeing my files?

They're encrypted, remember? Each file has an automatically generated key which also tells where the file is located. You can share this "filecap" with anyone else you'd like to see the file.

TBC