needs a concept of client running on a particular machine
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
launchpadlib |
Triaged
|
Low
|
Unassigned |
Bug Description
If I look in https:/
Some of these are just stale, but sometimes I really do need multiple authorizations of bzr or hydrazine because I run them on different machines. This ought to be handled somehow in lplib and launchpad (or at least documented)
What I would expect to see is
Hydrazine (on grace), authorized 2010-01-01 ...
obviously you can hack around this by putting it into the user-agent string but that seems a bit gross.
If my laptop is stolen I want to revoke all the credentials that were issued to it, no more and no less.
This might slightly relate to the credential-
Changed in launchpad-foundations: | |
status: | New → Triaged |
importance: | Undecided → Low |
Changed in launchpadlib: | |
status: | New → Triaged |
importance: | Undecided → Low |