duplicity-team team mailing list archive

Thread
Date

Re: [Question #140813]: "secret key not available" after remove-older-than?

To: duplicity-team@xxxxxxxxxxxxxxxxxxx
From: edso <question140813@xxxxxxxxxxxxxxxxxxxxx>
Date: Sun, 09 Jan 2011 23:10:28 -0000
Reply-to: question140813@xxxxxxxxxxxxxxxxxxxxx
Sender: bounces@xxxxxxxxxxxxx

Question #140813 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/140813

    Status: Open => Answered

edso proposed the following answer:
again, because this is important. you will always need a secret key to encrypt to so duplicity can refresh your archive dir when it needs to. that it seems to work without one is a bug, read the link above.
consider changing your strategy to encrypt also to the sign key. this is easy because it is there anyways. simply add another

--encrypt-key=${GPG_SIGN_KEY}

to solve your current misery:

A: implement the above solution and do a new full
B: keep the old way but import your secret key and enter the pass in ssh-agent. this by the way works for the sign key as well. you wont have to define a PASSPHRASE env var then. 

ede/duply.net

-- 
You received this question notification because you are a member of
duplicity-team, which is an answer contact for Duplicity.