|
[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
[NMLUG] backup storage trade
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Aaron Birenboim wrote:
| On Tue, 2004-12-07 at 23:16, Jody Harris wrote:
|
|
|>come to think of it, the only thing we have to agree on is 1) that we
|>trade drive space, and 2) a key system for encryption.
|
|
| I don't think we will need 2).
| Yes, we need to provide access to the server, likely
| through an ssh key. Data encryption is on the burder
| of the user, not the server space provider.
|
| I don't care what you back-up on my system if its encrypted.
| I can't see how I'm liable for information backed
| up on my system, when I have NO WAY knowing what it is.
|
| If rsync (or something similar) is smart enough to
| just update changed BLOCKS of files, one could just
| run a local rsync to an encrypted FS-on-a-file, then
| back-up that file.
|
| I have my GPG keys on cd-rom, flash-drive, and paper
| hex-dumps in firesafe and safe-deposit box.
| They should survive anything short of a nuke in ABQ.
|
Ok, gang...I got duplicity to work...It isn't very well documented, but
it's simple and fortunately for me, it's written by the same guy who did
rdiff-backup, so I could kinda tell how that guy thinks.
So, if anyone's interested right away, email me privately and we'll get
things started out...I will only accept trades with other people running
duplicity, as *ALL* other backup methods I've found are unacceptable to
me for one reason or another.
duplicity does have a few dependencies. The client needs python, rsync,
gnupg (I think that covers it), and the only thing the server needs is a
properly configured ssh server with hostkey-auth.
- -Dan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBuPg+nURHNoE9YE4RAv9FAKCC3IpgvQSqY6msQG8J/vfprvK1jACgydOS
fSkdXuTg0Nn/RrD4T9t5CrE=
=QfUb
-----END PGP SIGNATURE-----
|
|
