duplicity-team team mailing list archive

[edso <question183711@xxxxxxxxxxxxxxxxxxxxx>]

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

    Status: Open => Answered

edso proposed the following answer:
On 06.01.2012 09:05, Douglas Choma wrote:
> Question #183711 on Duplicity changed:
> https://answers.launchpad.net/duplicity/+question/183711
> 
> Douglas Choma posted a new comment:
> I'm also experiencing this same issue.  I even attempted sending the
> passphrase through to GPG with the  --gpg-options parameter.
> 
> When attempting to resume from an incomplete backup, I always get this
> error...
> 
> gpg: public key decryption failed: bad passphrase
> gpg: decryption failed: secret key not available
> 
> Just to confirm that the problem isn't with GPG, I downloaded the
> difftar.gpg file and decrypted it with the same passphrase exported for
> my duplicity script.
> 

for some reason ken's answer didn't went through.. so here it is again.. ede
-->

Try restarting your gpg-agent.  It's not talking to duplicity.

gpg: encrypted with 4096-bit ELG key, ID AA5ACFC9, created 2010-12-14
"FM Duplicity (Backup Key) <netops@xxxxxxxxxxxxxxxxxx>"
gpg: public key decryption failed: Bad passphrase
gpg: decryption failed: No secret key
can't connect to `/root/.gnupg/S.gpg-agent': No such file or directory   <<<------ HERE!

...Ken

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