On Mon, Oct 31, 2016 at 07:33:14PM +1000, Alexander Zangerl wrote:
> b) until duplicity knows about the quirks of gpg2, you need to
> add the option --gpg-options="--pinentry-mode=loopback" to your duplicity
> invocation. i've just tested this here and it worked fine for a backup
> with sign key an
severity 842552 minor
thanks
On Sun, 30 Oct 2016 16:54:12 +0500, Andrey Rahmatullin writes:
>Only gnupg version 2.1.15-8.
this is a known issue in gpg2: gpg2 no longer properly
honors --passphrase-fd, well, or at least it's not honoring it
the way the documentation indicates. duplicity needs that
On Sun, Oct 30, 2016 at 09:11:23PM +1000, Alexander Zangerl wrote:
> >After one of recent changes in gpg packages the --sign-key option, if the key
> >has a passphrase, signing fails,
>
> hmm, that's not good news. thanks for the detailed report, but
> i've got a few extra questions: what version
On Sun, 30 Oct 2016 15:51:13 +0500, Andrey Rahmatullin writes:
>After one of recent changes in gpg packages the --sign-key option, if the key
>has a passphrase, signing fails,
hmm, that's not good news. thanks for the detailed report, but
i've got a few extra questions: what versions of gnupg and
Package: duplicity
Version: 0.7.10-2
Severity: important
After one of recent changes in gpg packages the --sign-key option, if the key
has a passphrase, signing fails, I've tried passing the passphrase via
SIGN_PASSPHRASE and inputting it t the prompt.
Steps to reproduce:
1. Create a new user na
5 matches
Mail list logo
