Re: Using gpg-preset-passphrase before running duplicity as a cron job used to work
Jakob Bohm via Duplicity-talk <[email protected]>
| Newsgroups | gmane.comp.sysutils.backup.duplicity.general |
|---|---|
| Organization | WiseMo A/S |
| Message-ID | <[email protected]> |
On 2024-09-30 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. I haven't tried that method, what I do (with duplicity 1.2.1) is to set TRUST_PASSPHRASE in the environment and let the python code compiled into duplicity handle it . > ... Enjoy Jakob -- Jakob Bohm, CIO, Partner, WiseMo A/S. https://www.wisemo.com Transformervej 29, 2860 Søborg, Denmark. Direct +45 31 13 16 10 This public discussion message is non-binding and may contain errors. WiseMo - Remote Service Management for PCs, Phones and Embedded _______________________________________________ Duplicity-talk mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/duplicity-talk