This Bug is still existing on Natty (15.03., with latest Updates).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
https://bugs.launchpad.net/bugs/137247
Title:
libpam-keyring broken on autologins
--
desktop-bugs
** Changed in: gnome-keyring
Importance: Unknown = Medium
--
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
Closing papercut task
** Changed in: hundredpapercuts
Status: Incomplete = Invalid
--
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.
--
Tor Klingberg said: Suggested solution: Make available to all users
enabled by default for wireless connections.
This fixed it for me.
--
libpam-keyring broken on autologins
https://bugs.launchpad.net/bugs/137247
You received this bug notification because you are a member of Ubuntu
Desktop
Just going to chime in on this -- I'm a new Linux user, and this was
first wall I hit in setting up my system. My situation is a bit
different than everyone above, in that I also use my machine remotely
via telnet. As soon as I had to reboot the machine, I wasn't able to
re-connect to it. When
Suggested solution: Make available to all users enabled by default for
wireless connections.
--
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.
--
I think this is a huge issue, especially for people coming from Windows
or Mac to Ubuntu, and wants to use Ubuntu on their laptop. It's a hassle
to have type in a password at every start-up.
I think the best way to handle this would be to have a small checkbox in
the password prompt box that says
I have the same problem, I ended up just using /etc/network/interfaces
to setup my network instead, however this is quite a hassle
--
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,
Keyring pasword is not asked only with wifi encripted conextion. Using
Ubuntu One happens the same. It's happens when auto-login is activated
and the system needs a password activated in the keyring. Writting the
password every time that your machine starts... is very boring!
--
libpam-keyring
I believe that this bug is falsely filed against libpam-keyring: it
should be filed (only) against gdm. The solution should be to add a
trigger for the auto-login checkbox, which tests whether the keyring is
used at all. If so, it informs the user about the security consequences
and changes the
I think the check is whether an *encrypted* keyring is being used. If
the keyring already has a NULL password, and is in the clear, then
nothing needs to be displayed.
An alternative to actually changing the key directly would be an
explanation of what needs to be changed, additional words about
The issue of prompting for an encrypted wifi network password appears to
be treated separately, and upstream gnome-keyring thinks this is not a
bug. Marking incomplete until this can be clarified.
** Changed in: hundredpapercuts
Status: Confirmed = Incomplete
--
libpam-keyring broken on
For hundredpapercuts, let's triage this if we can find a trivial way to
minimize password prompts on login when auto-login is used.
** Changed in: hundredpapercuts
Status: New = Confirmed
--
libpam-keyring broken on autologins
https://bugs.launchpad.net/bugs/137247
You received this bug
** Also affects: hundredpapercuts
Importance: Undecided
Status: New
--
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
I complete these steps some time ago and still works on new installs of 9.04.
these are from memory but i hope they can help you.
if you have this problem I set up a wireless network. Set my account to
auto-login. Whenever I start machine, I get a dialog that nm-applet
wants access to keyring,
On a fresh install of 9.04,
I set up a wireless network. Set my account to auto-login. Whenever I
start machine, I get a dialog that nm-applet wants access to keyring,
enter password.
I want the machine to start up, take me to the desktop, and connect to
the network without troubling me for
Thanks Collin, that worked for me (in Jaunty Ubuntu Netbook Remix).
I have an administrator user (me) and a non-administrator user (my kid).
I went to administration-Login window and set my kid's account to auto-login.
Then I right clicked the wireless applet, went to 'edit connections',
the
I've only been using linux for a week (openSuse 11.1) now so I don't know how
much the distros differ between each other... But I found this workaround in
the forums from Xafke:
Goto the control panel, click Network Connections, open the tab Wireless,
Select you're wireless network and click
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 seb...@ubuntu.com
wrote:
the bug description suggests that's not a bug but how it's supposed to
work the pam keyring integration
how did you try to set the password exactly?
--
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
Sebastien: fr me on 8.10, it also does not work. I set it up by
applicationsaccessoriespasswords and encryption keys, there I go
editpreferencespassword keyrings* - I have got two keyrings there,
login and default, when I try to set them to blank (i.e I type in the
old password and leave the new
that seems a bug in the seahorse password change not a gnome-keyring
limitation, setting the password to be blank after the first login where
it asks the keyring password works correctly
--
libpam-keyring broken on autologins
https://bugs.launchpad.net/bugs/137247
You received this bug
** Changed in: gdm (Ubuntu)
Assignee: (unassigned) = Canonical Desktop Team (canonical-desktop-team)
--
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
This sounds like it is not a bug, but by design behavior. Please re-open
if I am mistaken.
** Tags added: ct-rev
** Changed in: gdm (Ubuntu)
Assignee: Canonical Desktop Team (canonical-desktop-team) = (unassigned)
Status: Confirmed = Invalid
** Changed in: network-manager-applet
I don't think I understand; doesn't NM already have such an interface?
The only change would be to save the keys in a file instead of placing
them in the keyring. (And a single check-box option to toggle between
the two.)
I don't see why file-based keys would need anything more than what is
The problem is that it still doesn't work.
We (the users) don't know exactly what package is the culprit. You can change
the package if you know another one contains the error.
But the bug is *not* fixed, please change the status to that.
Test:
Connect to a wireless network, reboot - at
Maybe nm-applet could have an option *not* to use the keyring to store
the password? Just store it internally somehow?
** Changed in: network-manager-applet (Ubuntu)
Status: Invalid = New
--
libpam-keyring broken on autologins
https://bugs.launchpad.net/bugs/137247
You received this bug
that would be a *very* quickdirty hack IMO.
better do it right.
--
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
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
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
i dont see an issue for nm-applet here. please reopen and give a short
explanation why nm-applet is the problem here.
** Changed in: network-manager-applet (Ubuntu)
Status: New = Invalid
--
libpam-keyring broken on autologins
https://bugs.launchpad.net/bugs/137247
You received this bug
Still not fixed in 9.04 Jaunty (see also Bug #223076, which looks like a
dupe)
** Also affects: network-manager-applet (Ubuntu)
Importance: Undecided
Status: New
--
libpam-keyring broken on autologins
https://bugs.launchpad.net/bugs/137247
You received this bug notification because
Bryan,
I'd say that wireless passwords are a security issue, but Ubuntu has
tended to treat them as far more serious than they actually are.
Laptops commonly have confidential business or personal information, and
hopefully have a login password, a bios password, or a disk encryption
password to
I experience this problem in Intrepid. To reproduce:
1. assume you've got a fully installed Ubuntu Intrepid
2. set up your wireless internet to connect to your encrypted access point
3. make sure your login keyring (or default keyring) has a password, and set it
to unlock automatically on login
This is all because the ability to unsecure and secure individual items
living in keyrings is not granular enough/not available. Wireless
passwords are a security non-issue, mine is: kurogane. Wireless
passwords (and quite likely other such keyring-ed passwords) need to be
easily passed to an
run seahorse, go to the edit, preferences dialog, select the line you
want and click on the unlock password button
--
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
*Thank* you! Damn, I must have passed through that menu a dozen times...
--
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
you can use seahorse to change the gnome-keyring password no need to
build tools
--
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.
--
Hi! I'm trying to enter an empty password with Rich's trick above, but
I'm having trouble compiling pam-keyring-tool on amd64. Is there any
reason why this was removed from the repositories, or why it can't be
added back?
--
libpam-keyring broken on autologins
Having an empty password is a workaround but not a solution.
I also ran into this when setting up Ubuntu 8.10 on a laptop last week and
using the wifi...
--
libpam-keyring broken on autologins
https://bugs.launchpad.net/bugs/137247
You received this bug notification because you are a member of
Sebastien, how can I change the keyring password with Seahorse? On my
machine it displays only SSH keys, as far as I can tell, and I can't see
anything in the configuration about the keyring. Am I missing something?
--
libpam-keyring broken on autologins
https://bugs.launchpad.net/bugs/137247
Not for me, it doesn't. I upgraded a new Hardy system to Intrepid
today, and it's started demanding Enter login password to unlock
keyring after doing an autologin. It wasn't doing that in 8.04.1
before I did the upgrade.
This new system was going to be for my mother, who is not very computer-
And the pam-keyring-tool workaround didn't work for me either. I was
still being prompted for the login password.
However, it looks like I was finally able to get rid of the unlock
keyring prompt by using pam-keyring-tool -c and entering an empty
password (just hit ENTER) for the new password.
Agreed. I also have the problem that suddenly I have to enter my Password when
I want to ssh to a known host - ssh seems to lookup the password/Key in the
keyring - ant that is locked!
This problem is NOT solved.
I just have ONE keyring, that one that is unlocked at login time.
And somehow it
Everything seems to work great on Intrepid now.
--
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
Martin Pool: you can use seahorse to change your keyring password.
Launch seahorse, go to Edition → Preferences, then click on your “login”
keyring in the first tab (keyrings), and you will be able to change its
password with the related button in the dialog.
regards,
Olivier
--
libpam-keyring
Thanks Olivier.
Unfortunately I can't get there because of bug 275661, but I'll try
later.
I would say it's a usability bug if that's the only place to access this
function.
--
libpam-keyring broken on autologins
https://bugs.launchpad.net/bugs/137247
You received this bug notification because
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
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
Password is properly masked on hardy. As such, unsubscribing ubuntu-
security.
--
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
I think too the bug is still there. Its not only with wireless network
keys. Also Evolution email uses the keyring manager, so I still need to
submit a keyring password.
--
libpam-keyring broken on autologins
https://bugs.launchpad.net/bugs/137247
You received this bug notification because you
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.
--
But I think that the bug exist, the problem is that now the system don't
is secure.
The solution is say to system what applications don't go to keyring
system, or say to keyring manager what applications allow password
automatically without write the keyring password.
Sorry my english, I am
I can confirm that after upgrade to Hardy, disabling workaround and
setting empty keyring password everything works fine. Thanks! :)
--
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,
the hardy gnome-keyring version allows to use an empty keyring password
which should fix this issue
--
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
I marked this bug confirmed, because I've experienced this problem. It
is apparently intended functionality, according to the Gnome developers,
but I'd still really like to be able to connect to my secured wifi at
home without authentication using my laptop. I do believe Windows lets
you save a
The Gnome developers will say this is intended functionality because
the Gnome keyring is (supposedly) used for other things, and they don't
want it to be subverted by autologin. I would argue that if the Gnome
keyring is so sacred then WPA passwords and WEP keys shouldn't be kept
in the Gnome
For those using the pam-keyring-tool workaround but dont like their password
lying around in plain text, you can get a bit more security by converting the
script to an exectuable with shc:
sudo apt-get install shc
shc -f script.sh
once I execute the shc command I then get an unlock.x file. Do I
I just tried this and it worked. You could do the following:
mv unlock.x unlock.shc (use any name you want, but I'd use something more
meaningful than a .x extension)
chmod 500 unlock.shc
Now you should be able to call unlock.shc exactly the way you previously
called your unlock script, with
I can't say for sure why, but I just got a new laptop (Lenovo Ideapad
Y510), and no longer have this problem. It connects to my WPA2 home
network every time without issue.
--
libpam-keyring broken on autologins
https://bugs.launchpad.net/bugs/137247
You received this bug notification because
** Also affects: gdm (Baltix)
Importance: Undecided
Status: New
--
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
*** This bug is a duplicate of bug 181281 ***
https://bugs.launchpad.net/bugs/181281
How long can it take to fix this?
The original bug was opened in September, and we have at least 2 dupes (18128
and 159569).
IMHO, network-manager-gnome is already a bad enough wireless client (compare it
** This bug is no longer a duplicate of bug 181281
Allow access to Keyring manager with no 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 a bug contact for gdm
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.
The gdm task is open, no need to have several tasks listed. The pam-
keyring doesn't work because autologin doesn't use pam so this bug will
have to worked in gnome-keyring rather
--
libpam-keyring broken on autologins
https://bugs.launchpad.net/bugs/137247
You received this bug notification
Fair enough, it's not a bug, it's a misfeature as the guy above said.
Can we not have a private/public key scheme here? Somehow, I can't think
of the specifics. Something that allows root to unlock the password, but
in a secure way.
Even if a solution requires you to enter your password ones
There is already bug #181281 on gnome-keyring about this issue
--
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
pam-keyring-tool was part of the pam-keyring (!= pam-gnome-keyring)
package that has been removed from hardy
--
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
how is that not a duplicate of this bug?
and anyway, is pam-keyring-tool going to be included in hardy once
again? If not, may i ask why?
--
libpam-keyring broken on autologins
https://bugs.launchpad.net/bugs/137247
You received this bug notification because you are a member of Ubuntu
Desktop
*** This bug is a duplicate of bug 181281 ***
https://bugs.launchpad.net/bugs/181281
that's a duplicated
** This bug has been marked a duplicate of bug 181281
Allow access to Keyring manager with no password
--
libpam-keyring broken on autologins
https://bugs.launchpad.net/bugs/137247
Why is this bug flagged as won't fix ? As far as I understand the
solution with the pam-keyring-tool is considered a 'hack'.
A user should be able to set auto-login and have their default keyring
work as before. I have the same problem, where I'm asked to unlock the
default keyring (once), when
Well this is not really a bug, If you don't give your password to gnome-
keyring, it cannot unlock you keyring. using pam-keyring-tool could be a
workaround
--
libpam-keyring broken on autologins
https://bugs.launchpad.net/bugs/137247
You received this bug notification because you are a member
True, that it's not really a bug. It's a misfeature that does really
need to be fixed for Ubuntu to be able to enter the mainstream and
capture market share.
--
libpam-keyring broken on autologins
https://bugs.launchpad.net/bugs/137247
You received this bug notification because you are a member
This sounds much better. I assumed that both passwords should be blank
since you wrote blank (keyring) password and other password in blank..
Thanks for clarifying.
--
libpam-keyring broken on autologins
https://bugs.launchpad.net/bugs/137247
You received this bug notification because you are a
** Changed in: gnome-keyring
Status: New = Invalid
--
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
Upstream closed this bug as NOTABUG which would translate to launchpad won't
fix. However, they say it will be possible to have the keyring unlocked in next
gnome (which is going to be in Hardy) for the price of blank (keyring) password
and other password in blank.
I am not sure what to do with
IMHO it's crazy to have blank password even at home. Password in some
form requires to do something from user for administration actions what
is IMHO good. For me it's bug in pam-keyring and can be fixed only here
since gdm-autologin has no password to unlock keyring. Sad situation
--
password to keyring will be (or rather, it will be possible for it to
be)blank, not the user 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 a bug contact for gdm
upstream maintainer (http://bugzilla.gnome.org/show_bug.cgi?id=506356)
asks about the dialog not hiding password with asterisks. Does anybody
still experience it? I personally cannot reproduce it.
Bruce: do you still get two dialogues? I cannot reproduce that either.
--
libpam-keyring broken on
For those using the pam-keyring-tool workaround but dont like their password
lying around in plain text, you can get a bit more security by converting the
script to an exectuable with shc:
sudo apt-get install shc
shc -f script.sh
--
libpam-keyring broken on autologins
** Changed in: gnome-keyring
Status: Unknown = New
--
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
Leszek, do you know what would be the equivalent to
System--Preferences--Sessions for Kubuntu? I could only find Kmenu --
System Settings -- Session Manager, but it doesn't allow me to add a
command.
Thanks
--
libpam-keyring broken on autologins
https://bugs.launchpad.net/bugs/137247
You
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 member of Ubuntu
Desktop Bugs, which is a bug contact
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
Chad, Marcus: I think you are describing this bug:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/162710/
--
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
** Bug watch added: GNOME Bug Tracker #506356
http://bugzilla.gnome.org/show_bug.cgi?id=506356
** Also affects: gnome-keyring via
http://bugzilla.gnome.org/show_bug.cgi?id=506356
Importance: Unknown
Status: Unknown
--
libpam-keyring broken on autologins
Chad, Marcus - alternatively to what Leszek writes, you can start gnome-
keyring-manager, delete the keyring and create a new one. FOr automatic
unlocking ,the keyring must be the same as login password.
Sebastien: I do think that having the keyring password in plain text is
a security issue but
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
I have the same problem as Marcus. Everything worked fine on a clean
install until I changed my password. Now I login in with my new
password but then the keyring manager pops up and needs me old password.
I can not find a way to change the keyring password to match my new
password. Quite
I'd like to add some additional info that may be helpful to identify the
problem. I have a clean gutsy install on a laptop with WPA wireless. Everything
works fine. Now I changed the login password to another one using the system
administration/user and groups dialogue. From that moment on
Thanks a lot to Troels Faber and Leszek !
Troels Faber's workaround should obviously only be used on a local machine, but
it works great !
Greetings from Berlin/Germany,
Jobst
--
libpam-keyring broken on autologins
https://bugs.launchpad.net/bugs/137247
You received this bug notification
I have the same problem. Autologin is one of the most important features
for notebooks. it is way wiser to secure your data with a bios password,
anyone who knows how to use a usb stick or or ubuntu disk can damage you
this way.
I can easily login without any password. I can connect using
I had exactly the same bug on my newly installed Gutsy machine. Just
fresh install and at every reboot I was asked for password to unlock
keyring to establish wireless connection. I spend few hours digging
solution and nothing helped. Finally I've found this page and WOW.
pam-keyring-tool
I can add that current state of this package is incosistent with
automatic keyring info on network-manager help page (on official Ubuntu
help pages): https://help.ubuntu.com/community/WifiDocs/NetworkManager
--
libpam-keyring broken on autologins
https://bugs.launchpad.net/bugs/137247
You
So until it's fixed you can use pam-keyring-tool provided above by
Troels Faber. Just put it in some folder (let's say /usr/local/bin),
create small script (I created /usr/local/bin/un_lock ) with 2 simple
lines:
#!/bin/sh
echo YOUR_PASSWORD | /usr/local/bin/pam-keyring-tool -u -s
Then do sudo
the workaround stores your password in clear which is a real security
issue, users should not do this change
--
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
It's obvious for me that it's only workaround and only for home users
for which simplicity is key feature. So you have temporary solution and
choice to do it or not.
I personally have done it on my wife's notebook since it's simple
environment used by her only a home, without any sensitive data.
I have a workaround, I've used for some time now.
libpam_keyring used to to include an executable called pam-keyring-tool, which
can be used to open the keyring. Starting with Gutsy, pam-keyring-tool is no
longer included.
I downloaded the source and compiled the executable. It is used like
So in other words, due to this bug and/or feature it is impossible to
setup Ubuntu 7.10 to automatically login and connect to a wifi network
upon reboot.
Sorry, but this really needs to be fixed ASAP. I can't believe I'm the
only one having a machine on a wifi network that I sometimes reboot
** Changed in: gdm (Ubuntu)
Sourcepackagename: gnome-keyring = gdm
--
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
1 - 100 of 111 matches
Mail list logo
