2
I had the following encrypted message laying around on my computer from back when I was playing around with GPG (and in this case, Enigmail)
-----BEGIN PGP MESSAGE-----
Charset: ISO-8859-15
Version: GnuPG v2.0.20 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
.............+AWJjL0Un8xWK0lFgw26Oos
ynzsVjy9fZAVlzoVN3XgucjIG8guTrakLbbvF0aMwDIwUXb3x1b+4hGNmkx+TUQV
kE6WcnnJw5B+8/m3CQ+IxbalHKAOu7VRHZ7XJCvY6dLAIQGSmwx77S3TV4zKH5PR
p3e15GJbcM+Gfo9Ka8u6KtGZALEk9xsZjH3QmfyB66dARp4/u7gJZrJ9hd5bzXJ9
LfjEvqygdpTeak2etz+r90WbiC/P4mnXQoxz7s3m1nJESb6VcpipJFkfwFdl1BYx
0XVfY/uH/gkQGiPNQL.....................O87w==
=Cnbj
-----END PGP MESSAGE-----
If I attempt to run gpg --list-packets
or gpg --decrypt
on the message, I get the following output (with the "invalid character skipped" warning repeated about thirty times):
gpg: invalid radix64 character 2E skipped
gpg: invalid radix64 character 2E skipped
gpg: invalid radix64 character 2E skipped
gpg: invalid radix64 character 2E skipped
gpg: CRC error; A3E958 - 0A76E3
gpg: [don't know]: invalid packet (ctb=3a)
Why does GPG not like this message? What is wrong with it?
@jens-erat thanks for the edit, guess I still have a lot to learn :) – JohnKiller – 2014-11-14T21:54:36.763
-----BEGIN PGP MESSAGE----- Version: OpenPGP.js v2.5.13 Comment: https://openpgpjs.org , this was the problem , just remove and all will work.
– waza123 – 2018-03-09T14:07:46.513