Home → Beta →

GPGMail: pinentry showing much too often

• Edit

Mike davis

12 Feb, 2017 07:32 PM

when composing an email I pine entry continues to pop up repeatedly even though its been dismissed, there is no option to stop it, and it makes it impossible and frustrating to use my email..

The options recommended by peers was to disable “encrypt drafts” or to save my password in my keychain, or to increase the password cache time, but each of these has security impacts that I would rather not have to accept.

Expected
Pine entry should understand that being dismissed disables encryption of current drafts, this can be done by either not saving the draft to the server, or saving it in clearext with a warning.

macOS           10.12.2     16C68
GPG Suite       2017.1b2    31b 
GPGMail         2.7b2       1192b
GPG Keychain    1.3.3b1     1249b
GPGServices     1.11        916 
MacGPG2         2.0.30-1b2  887-
GPGPreferences  2.0.2b2     912b
Libmacgpg       0.7         775 
pinentry        0.9.7       4

1. Support Staff 1 Posted by Steve on 13 Feb, 2017 09:22 AM

   

   Hey Mike,

   welcome to the GPGTools support platform. Sorry you are having problems using GPG Suite.

   We have a ticket for this problem. I connected this discussion with the existing ticket. That means, should this discussion get closed, it will be re-opened as soon as the ticket is closed. That way you'll stay in the loop and get notified as soon as we have news. Feel free to open a new discussions should you run into further problems or need assistance.

   The described behavior is new to macOS 10.12 and the way Apple is loading messages on that OS. We hope to find a solution to work around that.

   All the best,
   steve

   • Edit

2. Support Staff 2 Posted by Steve on 19 Mar, 2017 10:57 PM

   

   Hi Mike,

   this issue has been fixed. If you want to test the fix, please download our latest nightly GPG Suite. That page also has sig and SHA1 to verify the download.

   Should the problem persist, please re-open this discussion and let us know. For more questions that are not related to this specific problem, you are welcome to create a new discussion any time.

   Best, steve

   Disclaimer: This is a development version which has not been thoroughly tested yet, so bugs or crashes are to be expected. Thanks for helping us test this fix.

   • Edit

3. Steve closed this discussion on 19 Mar, 2017 10:57 PM.