Home → Stable →

GPG Keychain: ".asc" files are assumed to be keys

• Edit

Tim

09 Jan, 2017 12:53 AM

When I open an encrypted message that's in a ".asc" file, GPG Keychain tries to import it as a key, and fails. I would like something similar to the "automatic" mode of the gpg2 command-line tool.

Steps to reproduce:
1. Make or receive an encrypted file with a ".asc" extension
2. Open it

Expected
MacGPG2 automatically recognises the content of the file as a key or encrypted message, and performs the appropriate action.
OR
There is a preference for the default action.
When the default action fails, the other action is attempted.

macOS           10.12.2     16C67
GPG Suite       2016.12b1   26b 
GPGMail         2.7b1       1179b
GPG Keychain    1.3.3b1     1249b
GPGServices     1.11        916 
MacGPG2         2.0.30      884 
GPGPreferences  2.0.2b1     908b
Libmacgpg       0.7         775 
pinentry        0.9.7       4

1. Support Staff 1 Posted by Steve on 19 Jan, 2017 07:59 PM

   

   Hi Tim,

   when dealing with OpenPGP messasges in .asc format there is the problem that asc can be both: an encrypted message or a key. There is no way of knowing until the included data is looked at. So here's what we did: you can define a default application to open this with. If the default application to open asc files is GPG Keychain, that app will open. If we detect that the data included is not a key, the data will be forwarded to GPGServices which will then attempt to decrypt.

   Is this not working as described for you?

   All the best,
   steve

   • Edit

2. 2 Posted by Tim on 19 Jan, 2017 08:52 PM

   

   If the default application to open asc files is GPG Keychain, that app will open.

   This works.

   If we detect that the data included is not a key, the data will be forwarded to GPGServices which will then attempt to decrypt.

   This does not work, and has not worked for me for at least the last few versions of Mac GPG.

   • Edit

3. Support Staff 3 Posted by Steve on 21 Jan, 2017 09:50 PM

   

   Hey Tim,

   thanks for the feedback. So what happens for you? In my test, the message indeed was forwarded to GPGServices. But instead of decrypting it, GPGServices tried to verify and that was not a good idea for an encrypted messege.

   GPGServices should be content aware and make appropriate decisions depending on that info. But that needs some dev time and love first. It is not implemented at the moment.

   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.

   Best,
   steve

   • Edit

4. Steve closed this discussion on 20 Apr, 2017 03:14 PM.

5. Support Staff 4 Posted by Steve on 24 Oct, 2018 10:24 AM

   

   Hi Tim,

   this issue has been fixed. If you want to test the fix, please download our latest hotfix GPG Suite. That page also has Signature file and SHA1 to verify the download. Thanks for helping us test this fix.

   Should the problem persist, please do let us know and re-open this discussion.

   Should you see trouble using GPG Suite in the future, don't hesitate to get in touch and open 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.

   • Edit

6. Steve closed this discussion on 24 Oct, 2018 10:24 AM.