Question #107216 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/107216
Aaron Whitehouse posted a new comment:
See updated information on this topic in this mailing list thread:
http://lists.nongnu.org/archive/html/duplicity-talk/2015-03/msg00022.html
--
You received
Question #107216 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/107216
edso posted a new comment:
The advantage to this approach over my understanding of your approach
(one host key, plus one admin key) is that, even if the hacker gets
access to the cleartext
Question #107216 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/107216
edso posted a new comment:
On smaller backup's I'd suggest going for fulls only, which never need a
private key, except for verifying/restoring.
this was meant of course for older duplicity
Question #107216 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/107216
Status: Open = Answered
edso proposed the following answer:
This was true until duplicity version 0.6.0 .. This version keeps the
necessary metadata for incrementing backups in an archive/cache
4 matches
Mail list logo