[pkg-gnupg-maint] Bug#846953: Bug#846953: gpg2 fails to decrypt with "No secret key" but gpg1 succeeds

[Daniel Kahn Gillmor]

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 is likely no longer due to lack of GPG_TTY).

cool, glad we got the passphrase-prompting bit sorted out.

on to the rest of it...

do you have
~/.gnupg/private-keys-v1.d/DFE35C37A3C37A72BEE31A2E55252BA2A1EB0A2C.key
?

is it (in)appropriately large compared to the other, smaller secret key
material?

(that path is derived from --with-keyrip, fwiw)

can you try turning up the logging for gpg-agent (log-file and
debug-level in ~/.gnupg/gpg-agent.conf, followed by restarting the
agent) and see if it reports anything differently?

Also, how did you generate such a large key?  gpg usually limits key
generation to sane lengths.

           --dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnupg-maint/attachments/20161205/e47ec032/attachment.sig>