OOPS using email interface with a expired gpg key
Bug #211830 reported by
Diogo Matsubara
This bug report is a duplicate of:
Bug #331877: Useless error message for mails rejected due to bad signature.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Invalid
|
Critical
|
Brad Crittenden |
Bug Description
As seen in OOPS-824CEMAIL1 an InvalidSignature exception was raised when a expired signature was used in the email interface.
Instead of recording an OOPS we should tell the user that his key is expired and because of that the email couldn't be processed.
The exception value is Signature couldn't be verified: (7, 153, 'Key expired')
A copy of the message can be found at: https:/
Recently:
* InvalidSignature: Signature couldn't be verified: (7, 9, 'No public key'): OOPS-978CEMAIL2
Changed in malone: | |
assignee: | nobody → intellectronica |
Changed in malone: | |
milestone: | none → 1.2.4 |
Changed in malone: | |
milestone: | 1.2.4 → 1.2.5 |
status: | New → Confirmed |
Changed in malone: | |
milestone: | 1.2.6 → none |
description: | updated |
description: | updated |
Changed in malone: | |
importance: | Low → High |
status: | Confirmed → Triaged |
description: | updated |
Changed in launchpad-foundations: | |
importance: | Undecided → Low |
Changed in launchpad: | |
importance: | Low → Critical |
Changed in launchpad: | |
assignee: | nobody → Brad Crittenden (bac) |
status: | Triaged → In Progress |
To post a comment you must log in.
This doesn't happen very often.