GPG key adding - emails confusing

The first situation could be a real bug, I'll verify it soon and let you know.
The other is related with "what is an GPG UID beyond a new email address ?", I can't see a reason to treat it different, but maybe it lacks some feedback when it includes your GPG key entry, which basically is done when you validade one of its UIDs.

When I'm adding a GPG key, what I care about at that moment is the GPG key. I want clear indication that adding it either succeeded, or has not happened yet. Adding the email address is part of the process, I can see that - but when the email address is added, I'd like to see that the key is there. Perhaps simply redirecting back to /people/me/+editgpgkey would do the trick, since I can see it there. Also, that is where I started so it makes sense to leave me there at the end.

I see your point, but you can't be redirect from "validating token" to "editing gpg", since the last requires Edit permission. Something trick would be to include this feedback information in own "validade token" page. Anyway, the current workflow should support the validation of a key which have all its UID already validade inside Launchpad. this can be done by sending the email containing the token to the preferredemailand also sending encrypted email, which I'm working on.

> I see your point, but you can't be redirect from "validating token"
> to "editing gpg", since the last requires Edit permission.

I don't see why this is a problem -- the user has Edit permission for his own key. Am I confused?

Suppose the normal workflow:
 * browser closed (not logged in LP), the user figured out he has new email
 * reading that email, the user click in the link,
 * browser open the page "validade you UID"
 * the user types the LP pass to validade, click OK
 * LP redirects him to user/+editgpgkey,
 * LP redirects him to +login because he isn't authenticated yet.
 * the user needs to type login/"same pass" again.

So, Redirect from an unauthenticated page as token/key to <user>/+editgpgkey might require user to type his password again, the same was typed for validate the token. It's just /ugly/ from my point of view ... Adding more GPG info than "number of imported keys" to Person Overview can satisfy your suggested workflow, then we can redirect to people/<user> . What do you think ?

Morgs, please check if the current versions offers the information/hints you were looking for when validating a GPG Key, since you 've already validated your key, the workflow will be kind of compromised, you need to deactivate and revalidate you key, and you will pass through a similart workflow.

Morgs, I'm very interested in close this bug ;) could you provide the required feedback ?

Hey Cprov,

Much much better. I'm happy :)

Morgan

linksys eg1032 for 9.04 jaunty driver

Seems solved, so setting status appropriately.