Question #681867 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/681867
Status: Open => Solved
Jake Herrmann confirmed that the question is solved:
Thank you for the reply. I'm guessing the --default-key option for gpg
is responsible for this behavior. From the man page:
"If there is no secret key available for any of the specified values,
GnuPG will not emit an error message but continue as if this option
wasn't given."
I tested this with the command:
gpg --default-key foobar --sign filename.txt
and confirmed that it defaults to an existing key. I didn't actually
check whether duplicity uses gpg's --default-key option, but it seems
very likely that this is the cause. Seems like odd behavior to me, but
not duplicity's fault.
--
You received this question notification because your team duplicity-team
is an answer contact for Duplicity.
_______________________________________________
Mailing list: https://launchpad.net/~duplicity-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~duplicity-team
More help : https://help.launchpad.net/ListHelp
