Unable to reactivate a sign-only gpg key in some cases

Bug #50578 reported by Daniel Silverstone
4
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Medium
Diogo Matsubara

Bug Description

If you perform all the following steps you'll end up with a deactivated key that can't be reactivated.

1) Register a sign-only PGP key and validate it
2) Deactivate that key
3) Ask for a re-validation of that same key but don't re-validate it
4) Go to your +editgpgkeys page and see that the sign-only key is not there anymore.

Revision history for this message
Diogo Matsubara (matsubara) wrote :

Currently is already possible to do that.

Changed in launchpad:
status: Unconfirmed → Rejected
description: updated
Changed in launchpad:
assignee: nobody → matsubara
status: Rejected → Confirmed
importance: Untriaged → Medium
Revision history for this message
Diogo Matsubara (matsubara) wrote :

Ignore the comment above. It was posted before the bug was edited and re-opened.

Changed in launchpad:
status: Confirmed → In Progress
Changed in launchpad:
status: In Progress → Fix Committed
Changed in launchpad:
status: Fix Committed → Fix Released
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.