Home → Stable →

10.6: Still getting "No pinentry" error, nothing decryptable

• Edit

carolyn

01 Nov, 2013 12:34 AM

GPGSuite 2013.10.22
10.6.8

Please describe your problem. Add as much detail as possible.

Nothing is decrypted - pushing the "decrypt" button does nothing. Using the service gives:

Failed decrypting 'encrypted.asc'
encrypted.asc — Decrypt failed! (No pinentry)
Code = 85

Please describe what you did expect instead

I expected the messages to decrypt, like they do with other GPG implementations in Linux and Windows :)

If you remember, please describe the steps leading up to the problem

I was running the previous version of GPGTools on OSX 10.5.x - it mostly worked, but occasionally it would fail to decrypt something, and I hoped that using the latest version with the new service mode would work. I purchased the osx upgrade to 10.6.8 and reinstalled the latest build of GPGTools today (31 Oct). Nothing worked - saw that it requires a reboot (this is a bug as the installer doesn't force this) - rebooted, still not working - nothing decrypts at all.

Output of gpg version:
gpg (GnuPG/MacGPG2) 2.0.22
libgcrypt 1.5.3
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: ~/.gnupg
Supported algorithms:
Pubkey: RSA, ELG, DSA, ?, ?
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
CAMELLIA128, CAMELLIA192, CAMELLIA256 Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2

/usr/local/MacGPG2/bin/gpg2 --version gpg (GnuPG/MacGPG2) 2.0.22
libgcrypt 1.5.3
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: ~/.gnupg
Supported algorithms:
Pubkey: RSA, ELG, DSA, ?, ?
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
CAMELLIA128, CAMELLIA192, CAMELLIA256 Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2

1. Support Staff 1 Posted by Luke Le on 01 Nov, 2013 12:37 AM

   

   Hi Carolyn,

   very sorry to see you're having such a bad experience with our tools.
   Could you please post the content of the ~/.gnupg/gpg-agent.conf file?
   That should hopefully shed some light on this.

   Thanks.

   • Edit

2. 2 Posted by carolyn on 01 Nov, 2013 12:42 AM

   

   Thanks Luke - I hope this can be resolved :)

   default-cache-ttl 600
   max-cache-ttl 7200

   • Edit

3. Support Staff 3 Posted by Luke Le on 01 Nov, 2013 12:44 AM

   

   Interesting, this seems to happen especially on 10.6.8 computers.
   We have to investigate why this keeps happening.

   Could you please add the following line to your gpg-agent.conf:

   pinentry-program /usr/local/MacGPG2/libexec/pinentry-mac.app/Contents/MacOS/pinentry-mac
   

   Then run:

   killall -9 gpg-agent
   

   And everything should be dandy. (at least I hope so)

   • Edit

4. 4 Posted by carolyn on 01 Nov, 2013 01:15 AM

   

   Still getting the same error (rebooted too):
   Failed decrypting 'encrypted-1.asc'

   encrypted-1.asc — Decrypt failed! (No pinentry)
   Code = 85

   I also tried encrypting a file to myself to make sure that worked, and it did, but obviously signing failed.

   • Edit

5. Support Staff 5 Posted by Steve on 01 Nov, 2013 01:28 PM

   

   Hi Carolyn,

   could you please run the debug scripts (the first bullet point in that listing).

   Then post the output into this discussion.

   Thanks, steve

   • Edit

6. 6 Posted by carolyn on 01 Nov, 2013 05:54 PM

   

   Hi Steve,

   Well... seeing as others seem to get this to work on Mavericks, I went ahead and upgraded last night. Many reboots and reinstalls later, it now it works fine for decrypting. However, encrypting has a few problems, so I'll look for other discussions on those issues.

   Thanks

   • Edit

7. Support Staff 7 Posted by Steve on 02 Nov, 2013 02:15 PM

   

   Carolyn, did you follow our Getting Started Tutorial?

   At which step are you running into trouble?

   Glad a few issues have been resolved already. Now let's fix the rest. :)

   • Edit

8. 8 Posted by carolyn on 02 Nov, 2013 03:18 PM

   

   Since I was upgrading from the previous version, I didn’t think that much would change! Also I have been using GPG on Windows and Linux for many years and haven’t had any of these usability issues.

   The main feature I miss is being able to select a key for an address that doesn’t have a key with a matching userid. It seems a strange choice to remove this from the UI and have it now only accessible from the command line.

   • Edit

9. Support Staff 9 Posted by Steve on 03 Nov, 2013 01:13 PM

   

   So how does this work on Windows, Linux? Could you describe that, since I'm not familiar with how the process works there.

   Maybe we can learn.

   • Edit

10. 10 Posted by carolyn on 04 Nov, 2013 03:02 AM

    

    It used to work in GPGTools by just using the "Choose..." option when enabling encryption for a message. If an address didn't match a key, you could select a key. That select-ability is gone now.

    In Enigmail, you can similarly set a rule to use a specific key with a specific address -- effectively the same as the gpg command line, but you're prompted to do it from the GUI the first time you select the key.

    • Edit

11. Support Staff 11 Posted by Steve on 14 Nov, 2013 09:45 PM

    

    Hi Carolyn,

    the problem should be fixed. Could you please download and install our latest nightly build and see if the problem persists.

    All the 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

12. Steve closed this discussion on 14 Nov, 2013 09:45 PM.

13. Steve closed this discussion on 30 Dec, 2014 06:39 PM.