Re: [Duplicity-talk] Restore does not need the encrypt-key ?

[Tom]

Ahhhh I finally understand what was going on.
I would have been a little disappointed to learn that my backup were
unencrypted...

Thanks Kenneth and Edgar for having taken the time to answer me and to
provide additional infos.

Regards,
-- 
Tom




On Sat, May 8, 2010 at 14:09,  <address@hidden> wrote:
> gpg autodetects keyid and uses it if it's in your keyring.
>
> you can test this behaviour like this
> gpg -e -r 'gpg uid' -o test.data.gpg test.data
> gpg -d -o test.data.gpg test2.data
>
> check your keyring
> gpg --list-keys
>
> remove it from your keyring (--delete-secret-keys) and you should be
> unable to restore. You should backup it first (--export-secret-keys +
> --export).
>
> ..ede/duply.net
>
> On 08.05.2010 13:21, Tom wrote:
>> You are right, the seahorse-agent was running and also the gnome keyring.
>> I killed them but I still can restore without any info but the gpg 
>> passphrase.
>> The encrypt-key is not required.
>>
>> Additional info :
>> - Version "duplicity 0.5.09 running on linux2" on an Ubuntu 9.04.
>> - I don't have anything in ~/.cache/duplicity
>> - command line for backup :
>>     duplicity --encrypt-key 5690C020 --sign-key 5690C020 $include
>> $exclude /home/tom/ ssh://address@hidden
>> - command line for restore :
>>     export PASSPHRASE="something"
>>     duplicity restore ssh://address@hidden /home/tom/restore
>>
>> Thanks for any tips,
>
>
>
> _______________________________________________
> Duplicity-talk mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/duplicity-talk
>