-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
The plot thickens. When I try to encrypt something with a key whose
password is shorter than the crash-length, I get a popup saying:
Send operation aborted.
Error - encryption command failed
If I click Cancel instead of entering a password, Enigmail prepends
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
but has no appended cryptoblock. GNOME then crashed moments later, but
that might've been a coincidence? I think it had something to do with
Enigmail/pinentry/gpg-agent though. As always, having the debugging
gpg-agent open completely removes all traces of a problem.
On 09/01/2015 01:48 AM, Nathan Ringo wrote:
> When I'm typing my password into pinentry, it crashes partway
> through. Enigmail then says "no matching private/secret key found
> to decrypt message". When I run
>
> gpg-agent --debug-level expert --use-standard-socket --daemon
> /bin/sh
>
> as proscribed in the support page, the problem ceases to exist. I
> can use command-line gpg with graphical pinentry just fine. The
> combination of these two factors makes me suspect that the issue's
> in how Enigmail connects to gpg-agent, but I might be wrong.
>
_______________________________________________
enigmail-users mailing list
[email protected]
To unsubscribe or make changes to your subscription click here:
https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
