← Back to issue list

Missing account-key revocation support

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1800825
Type
issue
State
open
Author
~adam-collard
Labels
account-key
Created
Updated
Closed
—

Current evaluation

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.

Suggested action: close stale

Reason: Last activity was 2734 days ago with zero comments and no maintainer engagement. The interim suggestion references the old ~/.snaps/gnupg key layout and a 2017 forum thread, both long outdated, and the core revocation capability is a store-side feature that would need to be re-evaluated fresh rather than carried forward from this 2017-era request.

Impact: 40 Quick Win: 10.0 Staleness: 95 Complexity: 75 Confidence: 55 Support Request: 10

Issue body

As we can see in https://forum.snapcraft.io/t/snapcraft-register-key-failing/7732, store developers can very easily lose their private keys, even before they could sign anything with them. For those cases, a destructive form of key revocation (when all signatures are invalidated) would probably work. A more selective form of key revocation (when signatures prior to the action are considered valid) requires more elaborate support for timeproofs. In the interim, `snapcraft` CLI could be more informative about how to backup and restore keys (from `~/.snaps/gnupg`) and key-name conflicts.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 40
Quick Win: 10.0
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.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 40
Confidence: 85
Support Request: 15
close stale Feature request for account-key revocation and CLI key backup/restore improvements. Unaddressed for over 7 years with zero maintainer interaction.

Update history

No update history recorded yet.

Related work

  • Related To: snapcraft (launchpad)#1816524 (confidence 40%)

    Same key-management area (register-key failing), but about a different failure mode, not revocation.

  • Related To: snapcraft (launchpad)#2065075 (confidence 40%)

    Same key-management area (register-key timeout), tangentially related to key handling.

Related issues

Issue Project State Summary Similarity
#1669471 problems on revoking a gpg key for signing assertions snapcraft (launchpad) open snapcraft revoke-key prints usage help instead of revoking a GPG key (snapcraft 2.27.1). No comments or maintainer response for ~9.5 years. Version is long deprecated and store commands were reorganized under the snapcraft store subcommand.
72%
#1744013 snap does not support revocation of signing keys snapcraft (launchpad) open Reports that snapcraft's model assertion signing process (snap sign) provides no way to revoke signing keys. 8.6 years old with zero comments, no labels, and no maintainer interaction; unverified whether the store now supports key revocation.
71%