This bug was fixed in the package gnome-keyring - 2.21.5-0ubuntu1
---------------
gnome-keyring (2.21.5-0ubuntu1) hardy; urgency=low
* New upstream version:
- Proper support for creating and destroying objects through PKCS#11.
- Support for setting PKCS#11 attributes.
- Fix hanging of daemon under certain conditions.
- Add gconf setting for determining which components of the daemon
(such as SSH) are run at startup.
- Better parsing of objects and prompting for passwords in PKCS#12 files.
- Calculate trust and purpose/usage of certificates.
- Mark certain key/certificate directories as special requiring certain
special treatment
- Add support for unencrypted keyrings which are used when the user
specifies a blank password. (LP: #108993)
- Fix crasher
- Build fixes.
* debian/control.in:
- Build-Depends on libgconf2-dev
* debian/gnome-keyring.install:
- install new schemas
* debian/patches/80_from_upstream_fix_login_hang.patch:
- dropped, fixed in the new version
-- Sebastien Bacher <[EMAIL PROTECTED]> Tue, 15 Jan 2008 10:41:04
+0100
** Changed in: gnome-keyring (Ubuntu)
Status: Fix Committed => Fix Released
--
gnome-keyring-manager requires non-empty password
https://bugs.launchpad.net/bugs/108993
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
