Control: reassign 846953 gnupg-agent
Control: retitle 846953 gnupg-agent cannot deal with extremely large
passphrase-encrypted keys
Control: forwarded 846953 https://bugs.gnupg.org/gnupg/issue2857
On Mon 2016-12-05 11:24:08 -0500, Daniel Kahn Gillmor wrote:
> on to the rest of it...
>
> do you
On Mon 2016-12-05 09:40:38 -0500, Ryan Kavanagh wrote:
> I didn't have it set. Setting it now makes pinentry appear when I try to
> decrypt stdin (thanks!), but it unfortunately didn't fix the rest of the
> issue, e.g., I still can't decrypt files. (And I still can't decrypt
> stdin, though this
Hi Daniel,
On Mon, Dec 05, 2016 at 09:20:09AM -0500, Daniel Kahn Gillmor wrote:
> > rak@zeta:~$ echo "ABC" | gpg -r$GPGKEY1 --encrypt | gpg --debug 8 --decrypt
>
> do you have GPG_TTY set? if not, can you retry the first command after
> having done:
>
>GPG_TTY=$(tty)
I didn't have it set.
On Sun 2016-12-04 20:37:47 -0500, Ryan Kavanagh wrote:
> Guessing from the bug report and from the fact that
> ~/.gnupg/.gpg-v21-migrated is empty, the first command was supposed to
> be an rm on that file.
whoop, yes, you're right.
> rak@zeta:~$ echo "ABC" | gpg -r$GPGKEY1 --encrypt | gpg
Hi Daniel,
On Sun, Dec 04, 2016 at 07:08:34PM -0500, Daniel Kahn Gillmor wrote:
> Please try:
>
> ~/.gnupg/.gpg-v21-migrated
> gpg --list-secret-keys
Guessing from the bug report and from the fact that
~/.gnupg/.gpg-v21-migrated is empty, the first command was supposed to
be an rm on
Hi Ryan--
On Sun 2016-12-04 10:52:12 -0500, Ryan Kavanagh wrote:
> I'm unable to decrypt messages with gpg2, but can decrypt them with gpg1. See
> below for details. Please let me know if I can provide any further debugging
> information.
This sounds a lot like
Package: gnupg
Version: 2.1.16-2
Severity: important
I'm unable to decrypt messages with gpg2, but can decrypt them with gpg1. See
below for details. Please let me know if I can provide any further debugging
information.
Best wishes,
Ryan
rak@zeta:~$ echo $GPGKEY
4A11C97A
rak@zeta:~$ echo "ABC"
7 matches
Mail list logo
