On Thu, 18 Aug 2016 07:22, gni...@fsij.org said:
> In libgpg-error/doc/errorref.txt, it says:
>
> 18 GPG_ERR_WRONG_SECKEYWrong secret key used
BTW, the tool gpg-error is a quick way to get this data:
$ gpg-error 18
18 = (0, 18) = (GPG_ERR_SOURCE_UNKNOWN, GPG_ERR_WRONG_
On 08/17/2016 11:00 PM, Spoofy32 . wrote:
> --status-file outputs:
>
> [GNUPG:] ENC_TO 1 0
> [GNUPG:] GOOD_PASSPHRASE
> [GNUPG:] ERROR pkdecrypt_failed 18
> [GNUPG:] BEGIN_DECRYPTION
> [GNUPG:] DECRYPTION_FAILED
> [GNUPG:] END_DECRYPTION
>
> Is there a place where error code 18 i
--status-file outputs:
[GNUPG:] ENC_TO 1 0
[GNUPG:] GOOD_PASSPHRASE
[GNUPG:] ERROR pkdecrypt_failed 18
[GNUPG:] BEGIN_DECRYPTION
[GNUPG:] DECRYPTION_FAILED
[GNUPG:] END_DECRYPTION
Is there a place where error code 18 is defined?
On Wed, Aug 17, 2016 at 8:33 AM, Daniel Ranft wro
Am Dienstag, 16. August 2016 22:39:11 schrieb Spoofy32 .:
> The key IDs in the --list-keys outputs match between the private and public
> keys.
Given the round of fake keys that were available yesterday from a number
of keyservers, I additionally recommend checking and comparing the long keyid.
g
Apologies, I sent the previous email to the list before I finished typing
it (and I didn't have the undo send option enabled)! Please disregard that
email and my apologies for any inconvenience.
Actually intended text:
Greetings!
I am currently having an issue with decrypting a simple text file
