Missing account-key revocation support
Metadata
Current evaluation
Feature request (2020) for account-key revocation in snapcraft, plus interim CLI guidance on backing up/restoring GPG keys and key-name conflicts. Still unimplemented: no revoke-key command exists in snapcraft/commands/keys.py.
Suggested action: needs triage
Reason: The issue has 0 comments, no assignee, and no maintainer acknowledgement, and grep confirms no `revoke-key` command exists in snapcraft/commands/keys.py (only `register_key` in snapcraft/store/client.py:375 hitting /dev/api/account/account-key), so nothing has been implemented. The request is split into three separable asks — destructive revocation, selective revocation requiring timeproofs, and interim backup/restore messaging — and the selective form explicitly needs Store-side protocol support beyond snapcraft, which leaves scope and ownership undecided. It carries a single `account-key` label but no triage conversation. Note the repo has since gained real `create-key`/`register-key` implementations with KeyAlreadyExistsError/KeyAlreadyRegisteredError handling, so part of the 'key-name conflicts' ask appears addressed, but core revocation remains open and needs a maintainer decision on whether snapcraft or the Store owns it.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
35
Quick Win:
4
Complexity:
72
Confidence:
72
Actionability:
45
|
needs triage | Feature request (2020) for account-key revocation in snapcraft, plus interim CLI guidance on backing up/restoring GPG keys and key-name conflicts. Still unimplemented: no revoke-key command exists in snapcraft/commands/keys.py. | |
| stealth/space-bunny-alpha |
Impact:
52
Quick Win:
7
Complexity:
75
Confidence:
80
Actionability:
52
|
needs triage | Account-key revocation and backup/restore guidance need ownership and implementation triage; the old report has no maintainer discussion, and related Launchpad reports still request support or defer to snap/Store tooling. | |
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
10
Staleness:
95
Complexity:
75
Confidence:
55
Support Request:
10
|
close stale | Feature request for account-key revocation in snapcraft (destructive or timeproof-based selective), plus better CLI guidance on key backup/restore. Open ~7.8 years with zero comments and no maintainer interaction; interim suggestion likely outdated. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
70
Confidence:
90
Support Request:
20
|
close stale | Request for account-key revocation functionality in snapcraft to handle lost private keys, plus improved CLI documentation for key backup and conflict resolution. No maintainer response or activity in over 7 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
60
Confidence:
85
Support Request:
30
|
close stale | Feature request for account-key revocation and improved CLI key management in Snapcraft. Open for over 7 years with zero maintainer interaction or updates. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
60
Confidence:
85
Support Request:
40
|
close stale | Feature request for account-key revocation and improved CLI key management guidance. Unaddressed for over 7 years with zero maintainer interaction or comments. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
snapcraft#6144
(confidence 40%)
Commit 30c9fcd19 'refactor: migrate keys command (#6144)' reworked the keys command that the backup/restore guidance ask would touch, but adds no revocation support.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1669471 problems on revoking a gpg key for signing assertions | snapcraft (launchpad) | open | Ubuntu Store advertised a nonexistent Snapcraft revoke-key command; maintainers marked it high priority, and current key commands still omit key revocation. |