Re: [Bug 137247] Re: libpam-keyring broken on autologins
Sebastien, Sorry, but in a fresh 8.10 installation I made this week,* empty passwords are not accepted*. Cenora On Tue, Mar 10, 2009 at 5:53 PM, Sebastien Bacher wrote: > the bug description suggests that's not a bug but how it's supposed to > work the pam keyring integration works if you supply a password, if you > don't it ask for it or you can set an empty keyring password to not be > asked after login > > -- > libpam-keyring broken on autologins > https://bugs.launchpad.net/bugs/137247 > You received this bug notification because you are a direct subscriber > of the bug. > -- libpam-keyring broken on autologins https://bugs.launchpad.net/bugs/137247 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 137247] Re: libpam-keyring broken on autologins
On Tue, Feb 17, 2009 at 12:08:22PM -, Bogdan Butnaru wrote: > You know, I've been hearing this ever since NM appeared, and I still > don't understand why. SSH keeps *private*keys* in plain text files, > protected by nothing but file & folder permissions (it allows users to > enter a passphrase, but doesn't even protest if they don't). > > I don't see why WPA network keys are that much more secret than private > keys that doing the same would be *very* quick and dirty, especially > since they're almost always shared between several people. > the dirtry hack is not that it would be insecure. the dirty part is that users have to dive into the mutt of .pref directories in their home directory to find the right place to edit their keys - or the app has to provide a complete key management frontend ... which usually is too heavy weight all but a few apps. - Alexander -- libpam-keyring broken on autologins https://bugs.launchpad.net/bugs/137247 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 137247] Re: libpam-keyring broken on autologins
I've been informed by the friendly people in the #ubuntu+1 channel on IRC that Network Manager in Intrepid does not currently save the wireless network keys. You have to enter them every time you start Ubuntu. I was told it was a very common known issue which was expected to be fixed in time for the Intrepid beta release. On Thu, Sep 25, 2008 at 7:57 PM, Martin Pool <[EMAIL PROTECTED]> wrote: > >Solved in Ubuntu Hardy Heron 8.04 with this steps: > >1) System - Administration - Login window: Security tab, Enable automatic > login and select your user > >2) Delete files: rm ~/.gnome2/keyrings/* > > > > When restart system, write the WEP password for your wifi and don't use > password in keyring. > > Is there any way to change the keyring password without deleting the > whole keyring? In intrepid there does not seem to be any utility to > manage the keyring, though there was in hardy. > > -- > libpam-keyring broken on autologins > https://bugs.launchpad.net/bugs/137247 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in GNOME keyring services: Invalid > Status in "gdm" source package in Ubuntu: Confirmed > Status in "pam-keyring" source package in Ubuntu: Won't Fix > Status in "gdm" source package in Baltix: New > > Bug description: > Binary package hint: libpam-keyring > > This is on up-to-date Gutsy: > > libpam-keyring doesn't work correctly when set-up together with gdm's > autologin feature. > > As expected, GDM logins automatically the correct user. However > libpam-keyring fails to retrieve the user's password (probably because it > wasn't entered) and instead displays a dialog box asking for it, which > defeats the purpose of the plugin. Instead, if the password isn't available > it should just do nothing (perhaps log a message somewhere) and allow the > normal keyring unlocking to work (eg, let Network Manager ask for the > password when it needs it). This locks the loading process, which is very > annoying. > > Also, the dialog where libpam-keyring asks for the password does NOT mask > the entered password (eg, with asterisks), making it visible on the screen. > That's why I'm marking this as a (minor) security vulnerability. > > Note: of course this can be worked-around by simply disabling the plugin in > /etc/pam.d/gdm-autologin (and it doesn't put itself there), but it's still > buggy behavior. > > It's likely that libpam cannot actually retrieve the password on autologins > (I assume GDM just "su -"s into the username, so it doesn't actually know > the password), in which case this should be attached as a "wishlist" bug for > GDM or gnome-keyring. For instance, gnome-keyring might allow itself to be > unlocked by the "root" user as an optional, lower-security feature. > > Here's my config: > > $ cat /etc/pam.d/gdm-autologin > #%PAM-1.0 > authrequisite pam_nologin.so > authrequiredpam_env.so readenv=1 > authrequiredpam_env.so readenv=1 envfile=/etc/default/locale > authrequiredpam_permit.so > authoptionalpam_keyring.so try_first_pass > @include common-account > session requiredpam_limits.so > session optionalpam_keyring.so > @include common-session > @include common-password > -- libpam-keyring broken on autologins https://bugs.launchpad.net/bugs/137247 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 137247] Re: libpam-keyring broken on autologins
On Tue, 2008-01-29 at 11:54 +, cenora wrote: > IMHO, network-manager-gnome is already a bad enough wireless client (compare it to Intel's PROSet/Wireless, where you can see hidden SSID networks, manage profiles, etc). Interestingly, Intel's PROSet/Wireless is non-free Windows software. Nothing forces you to use something "better" than NetworkManager if you want to. There aren't many Ubuntu developers, and they aren't here just to fix the bugs you want fixed. -- Bruce Cowan <[EMAIL PROTECTED]> -- libpam-keyring broken on autologins https://bugs.launchpad.net/bugs/137247 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gdm in ubuntu. -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 137247] Re: libpam-keyring broken on autologins
Thanks for the info, will do in future. Philip Steiner w: 604-231-2003 h: 604-275-0803 c: 604-617-4612 - Original Message From: Bruce Cowan <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Sent: Sunday, December 30, 2007 1:35:58 PM Subject: [Bug 137247] Re: libpam-keyring broken on autologins Please don't use bug reports as support forums, if you want to ask someone a question, e-mail them directly. -- libpam-keyring broken on autologins https://bugs.launchpad.net/bugs/137247 You received this bug notification because you are a direct subscriber of the bug. Connect with friends from any web browser - no download required. Try the new Yahoo! Canada Messenger for the Web BETA at http://ca.messenger.yahoo.com/webmessengerpromo.php -- libpam-keyring broken on autologins https://bugs.launchpad.net/bugs/137247 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gdm in ubuntu. -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 137247] Re: libpam-keyring broken on autologins
Utility provided by Troels Faber has also functionality to change keyring password so you can use it to do it. I don't understand why it has been removed from gutsy when it's part o original package and was provided in feisty. BTW you're lucky that everything works for you on clean install. I'll install new system in few days so I can chceck it myself. -- libpam-keyring broken on autologins https://bugs.launchpad.net/bugs/137247 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gdm in ubuntu. -- desktop-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
