Branches for Lucid

Name Status Last Modified Last Commit
lp://staging/ubuntu/lucid-proposed/gnome-keyring bug 2 Mature 2010-07-29 16:04:26 UTC
105. * debian/patches/90_git_keyring_encod...

Author: Sebastien Bacher
Revision Date: 2010-07-28 17:45:40 UTC

* debian/patches/90_git_keyring_encoding.patch:
  - git change to fix an encoding issue in the default keyring name storage
    (lp: #553759)

lp://staging/ubuntu/lucid-updates/gnome-keyring 2 Mature 2010-07-28 17:45:40 UTC
105. * debian/patches/90_git_keyring_encod...

Author: Sebastien Bacher
Revision Date: 2010-07-28 17:45:40 UTC

* debian/patches/90_git_keyring_encoding.patch:
  - git change to fix an encoding issue in the default keyring name storage
    (lp: #553759)

lp://staging/ubuntu/lucid/gnome-keyring bug 1 Development 2010-04-22 17:14:18 UTC
101. * Drop 04_clean_session_keyring.patch...

Author: Martin Pitt
Revision Date: 2010-04-22 09:15:53 UTC

* Drop 04_clean_session_keyring.patch: This was a cleanup for users who
  installed Lucid Alpha versions and persisted until after Beta-2 and RC. No
  need to keep this extra code for the final release.
* Add 04_dont_save_login_password.patch: Disable writing the login password
  into the "login" keyring as "Unlock password for: User Keys". It was never
  meant to be there in the first place (it just was an inadvertent side
  effect of the code reorganization in 2.29), and a freely accessible
  cleartext password for each application once the keyring is unlocked
  creates a root escalation path through sudo. Also, remove that particular
  key entry on upgrades. (LP: #566046)

13 of 3 results