0

I'm switching from using deja-dup to just using duplicity, but backups fail due to "gpg: decryption failed: bad key".

Here is the script I made to put in my crontab: https://hastebin.com/piwupitiku.bash

When this script is run, it always fails with this:

GPGError: GPG Failed, see log below:
===== Begin GnuPG log =====
gpg: AES encrypted data
gpg: encrypted with 1 passphrase
gpg: decryption failed: bad key
===== End GnuPG log =====

I can verify that the PASSPHRASE environment variable is set before duplicity runs. What am I doing wrong?

I do NOT want to change how my backups are currently encrypted. I know that using gpg keys is better that what deja-dup does by default.

  • I have some gpg-encrypted files as well as mainly unencryped ones, but I don't use deja-dup or duplicity for back-ups. I use grsync and everything backs up quickly without an issue. No need for a crontab. – Paul Benson Feb 15 at 20:05

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.