Re: [Enigmail] pinentry crashes, only on Enigmail?
To the best of my knowledge, not unless I've started Thunderbird first. > Is there a gpg-agent running on your system before you start > another gpg-agent using the standard socket ? > > Patrick > > - Original Message - From: Nathan Ringo gmail.com> Sent: 02.09.2015 - 21:54 To: enigmail-users at > enigmail.net Subject: Re: [Enigmail] pinentry crashes, only on > Enigmail? > >> 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 enigmail-users at enigmail.net To unsubscribe or >> make changes to your subscription click here: >> https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net ___ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] New enigmail tries to decrypt with outdated, disabled key
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 03.09.15 09:32, Lars Noodén wrote: > On 09/03/2015 10:02 AM, Lars Noodén wrote: >> On 09/02/2015 11:24 PM, Patrick Brunschwig wrote: > ... >>> Please follow this guide to ensure it's working properly: >>> https://enigmail.net/support/gnupg2_issues.php > ... >> Thanks for the link to the guide. It mentions the GnuPG 2.x >> requires an agent to handle the passphrases. > ... > > That led to the solution. > > Thanks again to all who answered or thought about it. It turns out > the problem was in ~/.gnupg/gpg-agent.conf When this account lived > on another machine, I had been dual booting with OS X and Ubuntu > 14.04 The settings in gpg-agent.conf were for OS X and the earlier > versions of Engimail on Ubuntu were fine with that. The contents > were: > > default-cache-ttl 300 max-cache-ttl 99pinentry-program > /usr/local/MacGPG2/libexec/pinentry-mac.app/Contents/MacOS/pinentry-mac > > pinentry-program > /usr/local/MacGPG2/libexec/pinentry-mac.app/Contents/MacOS/pinentry-mac > > It was probably that last line causing the problem. > > Simply moving the file away solved the current problem. If I go > back to dual booting (unlikely) in the future, I will have to solve > anpther problem. Don't worry. Recent versions of GpgTools on OS X can live without this entry in gpg-agent.conf. - -Patrick -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJV6GRHAAoJENsRh7ndX2k7y2EP/RWcA/MgZG4lrl9VKy4KI81P BLiGYeG9zZetXQ//qfljqsxu2B9MGsd+hnsavwoEYdD55PX061MxPefdEv/2JrKF u4QDfNB1XUXd8PTxKz0anlIvX3sSS3Zt9ajRmbAmAbe2vUIIJ2TzgRYMGEtcV86x XWF1MrGwMM5jdqyktR2TfVEYRHVaHqtBGps4jJHHVwUaTMEn473ZTrn7PKDx4eOB Mg8UrxTS1OiLUrMGE78GhetRbSTULlh5SdUNUUP5n5X/clbina8fk4jpqjTK9BPx X6b2vZiGmaVq0t3KntqRj/04bDQXJNbdyiMQmrttkSHdg4+TRTf7r/plhSWnjNHd uhQ2D9cClWjxZ8HGPC97u2kHuXyJCZJmP9ftGlzdA+WBw7S6nupnfOHcRNnZnRJt CteQ1T40kwYNSPKd+eouLfPAzaCXDQ7jFR76Iohd/epw8TlXSTO0OMMY7Fanmmxx 7+J2UmMN9IrsoxMDV3xSVn4d5jF4U3K8+8XAGWFYLyXCMUUzwSFGVgPbv7G3gmKz Hq1FsDIH4+ImVoagSwQh6XQ1+YnfD4JBqWLnaWJ20FQ/Uj2ndMjGiGOVH6hcM24o 854MXH/ESZMuPrTCamcU0HkIOfUkINalroppxMHA1zEQ4ON1NU1tqraZruvYxpnQ 4mO1oVQIjGryAGjlgI3F =PifY -END PGP SIGNATURE- ___ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] New enigmail tries to decrypt with outdated, disabled key
On 09/03/2015 10:02 AM, Lars Noodén wrote: > On 09/02/2015 11:24 PM, Patrick Brunschwig wrote: ... >> Please follow this guide to ensure it's working properly: >> https://enigmail.net/support/gnupg2_issues.php ... > Thanks for the link to the guide. It mentions the GnuPG 2.x requires an > agent to handle the passphrases. ... That led to the solution. Thanks again to all who answered or thought about it. It turns out the problem was in ~/.gnupg/gpg-agent.conf When this account lived on another machine, I had been dual booting with OS X and Ubuntu 14.04 The settings in gpg-agent.conf were for OS X and the earlier versions of Engimail on Ubuntu were fine with that. The contents were: default-cache-ttl 300 max-cache-ttl 99pinentry-program /usr/local/MacGPG2/libexec/pinentry-mac.app/Contents/MacOS/pinentry-mac pinentry-program /usr/local/MacGPG2/libexec/pinentry-mac.app/Contents/MacOS/pinentry-mac It was probably that last line causing the problem. Simply moving the file away solved the current problem. If I go back to dual booting (unlikely) in the future, I will have to solve anpther problem. Regards Lars ___ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] New enigmail tries to decrypt with outdated, disabled key
On 09/02/2015 11:24 PM, Patrick Brunschwig wrote: > I doubt gpg2 is correctly set up on your PC, since you're not prompted for a > password. > > Please follow this guide to ensure it's working properly: > https://enigmail.net/support/gnupg2_issues.php > > Patrick Hmm. gpg2 was set up automatically however Ubuntu 14.04 does it. It seems to work manually. And it turns out that Engimail *is* trying the right key but fails. Here is what the log says about that: [GNUPG:] NEED_PASSPHRASE 6F87153B238909D7 1 0 gpg: problem with the agent: No pinentry [GNUPG:] ERROR get_passphrase 85 [GNUPG:] MISSING_PASSPHRASE gpg: encrypted with 4096-bit RSA key, ID , created 2014-03-24 " " gpg: public key decryption failed: Operation cancelled [GNUPG:] ERROR pkdecrypt_failed 99 [GNUPG:] BEGIN_DECRYPTION [GNUPG:] DECRYPTION_FAILED gpg: decryption failed: No secret key [GNUPG:] END_DECRYPTION Thanks for the link to the guide. It mentions the GnuPG 2.x requires an agent to handle the passphrases. I did change the settings on the agent a year or so ago because it was preventing SSH use by loading in all the ssh keys it could find, rather than the ones I would tell it to find, and then using them out of order causing the remote service to lock me out. If I have to choose between graphical use of SSH and Engimail, I must have the latter. So, the next step is for me to find the changes I did to the agent configuration and undo them, and see if that helps. Regards, Lars ___ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net