gpg CRC error in Validate your GPG Key email

Bug #1520 reported by Matt Galvin
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Invalid
Medium
Celso Providelo

Bug Description

I added my key to launchpad and was sent a confirmation email. When trying to decrypt that email I get the following error message from gpg:

--- snip ---
gpg --decrypt lp.txt
gpg: CRC error; 9FDFCF - DC39FD
gpg: quoted printable character in armor - probably a buggy MTA has been used

--- snip ---

NOTE: I use gmail and saved the original email to a file called lp.txt. I have been sent other encrypted emails via gmail and they have worked so I don't believe its an issue with gmail.

description: updated
Revision history for this message
Celso Providelo (cprov) wrote :

Uhm, as the message suggest, it is probably related to your MTA or mail reader, I can't see how to help you to solve this. I'd suggest you to forward me the email, but I can't do much about this either, except inspect the crypted message formatting. So, send me anyway, let's see how it looks.

Revision history for this message
Celso Providelo (cprov) wrote :

So, what `gpg` says was confirmed (what a surprise ?!), you've used the raw email message and it contains 'quoted printable' characters. The following python code can decode it:

{{{
>>> import email
>>> msg = email.message_from_string(raw_msg)
>>> body = msg.get_payload(decode=True)
}}}

`body` should contain the correct __decoded__ content.
Do not save the message, simply copy&paste the content redered by gmail, I suspect it will work.

Changed in launchpad:
assignee: nobody → name101
status: New → Rejected
Revision history for this message
Matt Galvin (mgalvin) wrote :

Not using the raw email worked. I copied just the encrypted content(from within gmail's web ui) to a file and decrypted it. It does appear to be a issue with the way gmail is handling the email. Sorry for the noise, thanks for the help. My gpg key is now in launchpad and useable :)

Revision history for this message
Phoenix (phoenix-dominion) wrote :

I just signed up and had the same Issue

-- 8< --
w3OqG+Dv3Wx6fNVESUpXCFFFC8X3HYyGk61ToThti0RejKGrDz7xqZbXHV+q3fKL
1TSV
=tD9k
-----END PGP MESSAGE-----
-- 8< --

This shows the last part of the message, The "=tD9k" looked fishy to me, so I removed it, and then I no longer got a CRC error and was able to decrypt the message.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.