Can't update PPA signing key descriptions

Bug #471225 reported by Julian Edwards on 2009-11-02
30
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Low
Unassigned

Bug Description

My PPA's (https://launchpad.net/~petri/+archive/ppa) signing key (1024R/075B83F9) ID reads "Launchpad Jansson". I would like it to be the standard "Launchpad PPA for Petri Lehtinen". Is it possible to revoke/delete the ID and add a new one?

tags: added: ppa
Changed in soyuz:
status: New → Triaged
importance: Undecided → Low
Abel Cheung (abelcheung) wrote :

For some people this problem might be more nasty than it sounds like. If PPA packages are for personal use, then most people can perfectly live with it; but if the packages are intended for more widespread use, then the signing key description can be more important. Say if I want to install package A, but found that the key description says the key is for package B, then it is perfectly reasonable to NOT trust the key.

Kamal Mostafa (kamalmostafa) wrote :

I have exactly the problem described by Abel in Comment #1 -- I foolishly named my very first PPA "fixes for aprsd", and now all my other unrelated PPA's bear a signing key labeled with "Launchpad fixes for aprsd" which is quite misleading. This is a problem for me. Even if I can't have control over the key comment, I'd like to be able to request a one-time change to replace the reference to aprsd with my name and/or userid.

Abel Cheung (abelcheung) wrote :

I have been gaming and toying the Launchpad system lately, but so far nothing worked. New accounts don't allow reusing GPG key from other a/c, PPA repos are not deletable once created, creating new a/c and merging with old one is a complete FAIL. Apparently the only way is to completely forfeit old a/c, and create new a/c with GPG key specific for PPA purpose. Of course, the management overhead is the big disadvantage here.

Anyway, others please feel free to game the system and see if anything else can be done.

Max Bowsher (maxb) on 2010-12-02
summary: - Can't update PPA signing key descriptions
+ Can't update PPA signing key descriptions, and the current UI makes it
+ too easy to create keys with poor description
William Grant (wgrant) wrote :

The key is now named after the person's displayname, not the archive's. So it's not easy to get it wrong.

summary: - Can't update PPA signing key descriptions, and the current UI makes it
- too easy to create keys with poor description
+ Can't update PPA signing key descriptions
William Grant (wgrant) on 2014-06-19
tags: added: gpg
Colin Watson (cjwatson) wrote :

I think this would be one of the things that would be easier to fix if we brought PPA signing keys into the Launchpad database with best-effort syncing to the keyservers, as we've been talking about recently. It would then be moderately possible/reasonable to have a job that syncs up key descriptions with current person/team names.

(This is arguably a data protection issue: it's one of the places where changing a user's display name isn't currently propagated everywhere, which is important for trans people among others.)

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions