Re: Using gpg-preset-passphrase before running duplicity as a cron job used to work
"edgar.soldin--- via Duplicity-talk" <[email protected]>
| Newsgroups | gmane.comp.sysutils.backup.duplicity.general |
|---|---|
| Message-ID | <[email protected]> |
1. do you provide `--use-agent` in your duplicity command line? if not, try to. 2. please state your versions. os, duplicity, gpg. sunny regards ..ede/duply.net On 30.09.2024 23:42, Henry S. Thompson via Duplicity-talk wrote: > but it doesn't anymore. Possibly because I upgraded gpg and/or > duplicity. Does this ring any bells for anyone/any suggestions for > getting it working again? > >> echo "KEYINFO --no-ask [keygrip] Err Pmt Des" | gpg-connect-agent > S KEYINFO [keygrip] D - - 1 P - - - > > The documentation says that '1' signals that the passphrase has been > stored successfully. > > But I get the following error in duplicity log: > > 2024-09-08_10:08:33: Skipping databases today > 2024-09-08_10:08:33: Backup for local filesystem started: local > 2024-09-08_10:08:33: ... backing up filesystem > Local and Remote metadata are synchronized, no sync needed. > Last full backup date: Thu Jun 13 23:27:14 2024 > Error processing remote manifest (duplicity-inc.20240629T010501Z.to.20240701T010502Z.manifest.gpg): GPG Failed, see log below: > ===== Begin GnuPG log ===== > gpg: encrypted with 3072-bit RSA key, ID [...], created 2024-06-13 > "Henry S. Thompson (For backup to markup /var/backups/maritain) <[email protected]>" > gpg: public key decryption failed: Bad passphrase > gpg: decryption failed: No secret key > ===== End GnuPG log ===== > > GPGError: GPG Failed, see log below: > ===== Begin GnuPG log ===== > gpg: using "[correct keyID as supplied to gpg-preset-passphrase" as default secret key for signing > gpg: signing failed: Bad passphrase > gpg: [stdin]: sign+encrypt failed: Bad passphrase > ===== End GnuPG log ===== > > 2024-09-08_10:08:59: Backup for local filesystem complete > 2024-09-08_10:08:59: ------------------------------------ > > Thanks for any ideas what to try to fix this. > > ht _______________________________________________ Duplicity-talk mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/duplicity-talk