Difference between revisions of "Talk:INTERNETARCHIVE.BAK"
Jump to navigation
Jump to search
m |
|||
Line 1: | Line 1: | ||
== A note on the end-user drives == | |||
I feel it is really critical that the drives or directories sitting in the end-user's location be absolutely readable, as a file directory, containing the files. Even if that directory is inside a .tar or .zip or .gz file. Making it into a encrypted item should not happen, unless we make a VERY SPECIFIC, and redundant channel of such a thing. --[[User:Jscott|Jscott]] 00:01, 2 March 2015 (EST) | |||
===Proposed solutions=== | ===Proposed solutions=== | ||
* [https://tahoe-lafs.org/trac/tahoe-lafs Tahoe-LAFS] - decentralized (mostly), client-side encrypted file storage grid | * [https://tahoe-lafs.org/trac/tahoe-lafs Tahoe-LAFS] - decentralized (mostly), client-side encrypted file storage grid |
Revision as of 05:01, 2 March 2015
A note on the end-user drives
I feel it is really critical that the drives or directories sitting in the end-user's location be absolutely readable, as a file directory, containing the files. Even if that directory is inside a .tar or .zip or .gz file. Making it into a encrypted item should not happen, unless we make a VERY SPECIFIC, and redundant channel of such a thing. --Jscott 00:01, 2 March 2015 (EST)
Proposed solutions
- Tahoe-LAFS - decentralized (mostly), client-side encrypted file storage grid
- Requires central introducer and possibly gateway nodes
- Any storage node could perform a Sybil attack until a feature for client-side storage node choice is added to Tahoe.
- git-annex - allows tracking copies of files in git without them being stored in a repository