Ubuntu
duplicity package

  1. Bug #379648
  2. Comment #1

Comment 1 for bug 379648

Revision history for this message
Jens Wilke (jw-launchpad) wrote :

Same problem here after trying an incremental backup after a full backup.

In my environment, it seems the PASSPHRASE variable is not recognized.

Debugging:
strace -s 128 -f duplicity .... > xy
grep GNUPG < xy

gives:
[pid 15476] write(4, "[GNUPG:] ENC_TO 37105F933226F 16 0\n"..., 38) = 38
[pid 15476] write(4, "[GNUPG:] USERID_HINT 37105F9C3216F backup key <email address hidden>\n"..., 99) = 99
[pid 15476] write(4, "[GNUPG:] NEED_PASSPHRASE 37105F9C3216F 62E7B190B96DE 16 0\n"..., 64) = 64
[pid 15476] write(4, "[GNUPG:] MISSING_PASSPHRASE\n"..., 28) = 28
[pid 15476] write(4, "[GNUPG:] BAD_PASSPHRASE 37105F9C3216F\n"..., 41) = 41
[pid 15476] write(4, "[GNUPG:] BEGIN_DECRYPTION\n"..., 26) = 26
[pid 15476] write(4, "[GNUPG:] DECRYPTION_FAILED\n"..., 27) = 27
[pid 15476] write(4, "[GNUPG:] END_DECRYPTION\n"..., 24) = 24
[pid 15469] read(4, "[GNUPG:] ENC_TO 37105F9C3216F 16 0\n[GNUPG:] USERID_HINT 37105F9C3216F backup key <dustbin@headiss"..., 4096) = 347

Hope that hint helps.

It's not clear to me where actually the PASSPHRASE variable gets evaluated.
In the sources of duplicity (/usr/share/pyshared/duplicity) I cant find a hint on it.