On Sat, 2007-04-14 at 10:07 +0200, Kirioss wrote: > > > -----Message d'origine----- > > > More design info here: > > > > > > http://live.gnome.org/GnomeKeyring/Cryptoki > > > > Regarding 'Certificate Storage' on that page, which looks > > like a still open question (or at least not yet closed), I > > want to give a +1 for using PKCS#12 for this purpose. Even > > if the format has its warts, it is much better than inventing > > a new format. > > Hi > > I'm not sure I understand what will be possible with this new function. Will > it be possible to unlock automatically the keyring when the user logon (to > avoid multiple passwords) and let NetworkManager (wireless and VPN) take the > certificate in the keyring without the need, for the user, to know any pin > code to unlock the private key ? > > If it is possible, it is a great function, because today, my users have to > know 3 passwords (gnome session, keyring and pin code). The session password > has to be changed every 90 days, users do not understand what a keyring is > (that's why I would like to unlock it automatically). It is very difficult, > after monthes, to remember what each password is for... >
You can use pam_keyring to unlock your gnome_keyring on login. You can get it at http://www.hekanetworks.com/pam_keyring/ . Tomorrow I am releasing the next version that will include support for changing the keyring's password. Hope that helps. Jon _______________________________________________ desktop-devel-list mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/desktop-devel-list
