[tahoe-dev] Privacy of data when stored on allmydata.com

Andrej Falout andrej at falout.org
Thu Feb 5 04:26:43 UTC 2009

Thank you very much François, it works beautifully.

And on small files it's many times faster then 'tahoe cp -r' too.

Small suggestion may be to add support for non-default (~/.tahoe) nodedir,
if possible?

However, this type of backup will force me to download complete full backup
tar file, and possibly several incremental backups, even if I need to
restore a single file.

Also, Duplicity needs, depending on compression efficiency, about a third of
the disk space free to perform a full backup [1]. Which unfortunately makes
it useless for me in most cases

I am wondering if it is possible to plug in encryption to FUSE mounter
(blackmatch), while we wait for private rootcaps ?


1: http://duplicity.nongnu.org/FAQ.html

On Tue, Feb 3, 2009 at 9:40 PM, Francois Deppierraz
<francois at ctrlaltdel.ch>wrote:

> Andrej,
> Andrej Falout wrote:
> > 1) tahoe cp -r ... is in that case not an option for any data that needs
> > to be secured. Does anyone have a suggesting of what to do so that all
> > files passed to tahoe client are allready encrypted?
> Yes, my duplicity tahoe backend [1] can do exactly that if you omit the
> "--no-encryption" option.
> > 2) I assume this will remove any chance of using rsync, Unison, or
> > simmilar to keep local disk and tahoe store in sync, and that the only
> > strategy for backups will be to do a full backup to a single encrypted
> > file, and then do differential backups? Which would mean that each file
> > that was changed will need to be uploaded completely, and not just the
> > parts that changed? And after restore, all files that where deleted sin
> > the meantime will reappear on restored file system? And files versioning
> > is out of the question?
> Shawn Wilden is currently working on a much better backup implementation
> which does versioning and much more. Have a look at this maling-list
> archives.
> However, the issue of giving your rootcap to allmydata.com is indeed
> important. According to this post [2] from Brian Warner, creating your
> own rootcap on the production grid is somewhat "supported" but I cannot
> find any official information about that.
> François
> [1] http://allmydata.org/pipermail/tahoe-dev/2008-November/000890.html
> [2] http://allmydata.org/pipermail/tahoe-dev/2008-November/000880.html
> _______________________________________________
> tahoe-dev mailing list
> tahoe-dev at allmydata.org
> http://allmydata.org/cgi-bin/mailman/listinfo/tahoe-dev

Andrej Falout
AU: +61 (410) 463 735 NZ: +64 (21) 0256 6825 US: +1 (360) 488 0970
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20090205/f6b9d0c8/attachment.html>

More information about the tahoe-dev mailing list