gpg metadata on inline signed bug mail is shown in web UI and forwarded in mail
Bug #161822 reported by
John A Meinel
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned |
Bug Description
When creating a new bug in Malone, you need to use a gpg-signed email (at least as I understand it).
However, the parser does not strip the GPG headers, so you end up with bug reports that look like bug #133751.
This is somewhat similar to bug #2653, but in a different vein.
It might also be possible to just hide them, like you do with hiding the quoted sections in replies. I would also recommend hiding control section:
X affects /products/bzr
X status triaged
X importance medium
See also bug 190758, about verifying the GPG signature.
Changed in malone: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
description: | updated |
summary: |
- new bugs by email requires gpg signature but does not strip it from bug - report + gpg metadata on inline signed bug mail is shown in web UI and forwarded + in mail |
Changed in launchpad: | |
importance: | Medium → Low |
To post a comment you must log in.
Would be nice to fold the PGP signature, just like the behavior with "-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA1" is.