On 23.11.2010 14:07, Kenneth Loafman wrote:
To guarantee that the remote and local caches are the same duplicity
compares the manifest files. The remote manifest is encrypted, thus the
need for the private key.
...Ken
On Tue, Nov 23, 2010 at 6:49 AM,<address@hidden> wrote:
In theory duplicity does not need the private key of a backups encryption
public key for incremental backup anymore. This is possible due to the
unencrypted contents of the archive dir.
In practice a duply user now stumbled over the following. I can reproduce
this.
Generate a key pair. Export it.
Delete the private key from your keyring.
Do an initial backup with duplicity.
Do a second backup or force an incremental backup. This fails with an error
like
"The matching private key is missing"
What is going on here. Can somebody more familiar with the encryption code
please confirm this behaviour. I tried version 0.6.06, 0.6.08 and 0.6.11 ..
none works as expected.
Commandline generated by duply is
TMPDIR='/tmp' /srv/www/vhosts/
jamoke.net/_apps/duplicity-0.6.06/bin/duplicity --encrypt-key DA3FEEDB
--verbosity '4' --exclude-globbing-filelist '/srv/www/vhosts/
jamoke.net/.duply/keytest/exclude' '~/duply_dev' 'file:///tmp/keyt3esrt'
thanks ede/duply.net
_______________________________________________
Duplicity-talk mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/duplicity-talk
_______________________________________________
Duplicity-talk mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/duplicity-talk
_______________________________________________
Duplicity-talk mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/duplicity-talk