Mechanism to synchronise the Launchpad local GPG key-ring
Bug #1458 reported by
Celso Providelo
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Won't Fix
|
Low
|
Unassigned | ||
Bug Description
It would be possible to use a small cronscript to synchronise all validated keys inside LPDB with their state in the global key ring. It doesn't represent a big issue but has a lot of corner-cases, that's why it needs specing and GPG gurus touching.
| Changed in foaf: | |
| assignee: | nobody → name101 |
| status: | New → Accepted |
| Changed in launchpad: | |
| assignee: | cprov → nobody |
| Changed in launchpad-registry: | |
| importance: | Medium → Wishlist |
| status: | Confirmed → Triaged |
Revision history for this message
| Celso Providelo (cprov) wrote | #1 |
| visibility: | private → public |
| Changed in launchpad: | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
Updating the GnuPG keys registered in LP would an opportunity for 1) adding new email addresses for the key owner (pending validation), 2) invalidating revoked address and 3) invalidating revoked keys.
TBH, I'm not really convinced it suffice as a rationale for implementing it. Possibly, there might be other cross-checks we can perform, but until now none of them seem compelling.