Home → Beta →

GPGServices: Encrypt/sign failed!

• Edit

Gonzalo Amador Demeneghi

07 Feb, 2017 06:42 PM

Hola, cuando trato de encriptar un archivo desde Servicios>OpenPGP Encrypt File, me aparece un mensaje de error que dice lo siguiente:

Encrypt/sign failed!
Code = 0

Después del mensaje mi archivo no queda encriptado. Ya he desinstaladlo y vuelto a instalar en OpenPGP, pero el resultado ha sido el mismo.

Expected
Esperaba que mi archivo estuviera encriptado y firmado.

macOS           10.12.3     16D32
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

• 2017-02-07_18-42_DebugInfo.gpg 12 KB

1. Support Staff 1 Posted by Steve on 18 Feb, 2017 01:42 PM

   

   Hey Gonzalo,

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

   Our spanish is really rusty. Can you repost your question in english?

   I am just assuming you are running into issues using GPGServices. So giving a very general answer here. Let's test gpg encryption and decryption in the terminal.

   1. click spotlight at the top right menubar and type 'terminal'
      
   2. open Terminal.app by pressing enter
      
   3. in the new terminal window
      
   4. paste the following without the ' 'gpg2 -ae --default-recipient-self <<<OK'
      
   5. a PGP message will be created
      
   6. paste the following without the ' 'gpg2 -ae --default-recipient-self <<<OK | gpg2 -d'
      
   7. you will be asked for your password (if your password is still in the cache or stored in the macOS keychain you will not be asked)
      
   8. when everything is fine you should see the word "OK" in your terminal - in that case decryption worked as expected

   Does that work for you?

   All the best,
   steve

   • Edit

2. Support Staff 2 Posted by Steve on 04 May, 2017 12:13 PM

   

   Closing, since no further user feedback was received. Should your problem persist, feel free to re-open this discussion any time.

   All the best, steve

   • Edit

3. Steve closed this discussion on 04 May, 2017 12:13 PM.