inline gpg can be corrupted by non-gpg aware mail clients (e.g. gmail)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
I submit 4cfcc785e7e9294
when I actually get an email message with a bad pgp message:
$ echo "-----BEGIN PGP MESSAGE-----
Version: GnuPG v1.4.10 (GNU/Linux)
hQIMAxq+
xWlW+ivoVRzEzzv
TZ2OiH6AvH8Q1sx
f7kr0aCkgBqn3DC
gzIeVbGxTa2MuGq
lCybB5Zm+
bGoIXQjeyKKaTje
8+Hnusv111+
yMOVkFec0jGWM1W
dHP8j4l6rPzY5cQ
AnyjMaZpU3gJox+
wK8BREKCe9fvpR7
LH1LFtESo9zp3gj
tFnroqAYnVAke9S
RZh1N6wJbpFAEwL
jwlfV+/
+CprA78hPvPtzG9
fit+9z1/
c9t6wVHh+
=3DmZwE
-----END PGP MESSAGE-----" | gpg
gpg: CRC error; 999C04 - DC3999
This may have been because I only had revoked keys available to encrypt with and it took till 4096R/B6D51144 got synced with the ubuntu keyserver to be added before it sent me a valid message
summary: |
- invalid crc PHP MESSAGE sent by editpgpkeys + sending pgp inline in plain text causes apparent crpc errors |
tags: | added: confusing-ui email gpg |
summary: |
- sending pgp inline in plain text causes apparent crpc errors + sending pgp inline in plain text causes apparent crc errors |
summary: |
- sending pgp inline in plain text causes apparent crc errors + inline gpg can be corrupted by non-gpg aware mail clients (e.g. gmail) |
Changed in launchpad: | |
importance: | High → Low |
I don't really understand what the problem is. Where did the message originate? What did you expect to happen?