Can we no longer unlock gnome-keyring on login if we don't use GDM?

pogeymanz · 2011-05-11 20:09:59

After the update to gtk3, gnome-keyring bothers me for my password when I log in (because of networkmanager).

There is a checkbox to automatically unlock the keyring at login, but it is disabled. Presumably because I'm not using GDM to log in. Any way around this?

P.S. All network managers suck for laptops.

Allan · 2011-05-11 20:34:36

I have no issues... What login manager are you using?

pogeymanz · 2011-05-11 21:53:19

startx

I launch nm-applet in Openbox's autostart file with

nm-applet --sm-disable &

It also doesn't work right without the --sm-disable option.

Butcher · 2011-05-11 22:35:48

pogeymanz wrote:

P.S. All network managers suck for laptops.

That's what I thought until I tried wicd

Allan · 2011-05-11 22:57:34

Do you have console-kit running?

matkam · 2011-05-12 09:24:23

I use startx as well. Added the following lines to /etc/pam.d/login file to unlock the keyring when you login through tty:

auth            optional        pam_gnome_keyring.so
session         optional        pam_gnome_keyring.so  auto_start

Last edited by matkam (2011-05-12 09:25:45)

guriinii · 2011-05-12 09:54:40

I had this problem for quite I while, which I couldn't solve, so I give in and installed wicd. Which I should've done from the start.

pogeymanz · 2011-05-12 12:11:42

matkam wrote:

I use startx as well. Added the following lines to /etc/pam.d/login file to unlock the keyring when you login through tty:
auth            optional        pam_gnome_keyring.so
session         optional        pam_gnome_keyring.so  auto_start

Ah, this is what I needed.

I actually saw this while googling, but the sites I saw it on were old (like 2007), so I assumed it would be barking up the wrong tree. I was wrong. After I did this, I had to delete one of my saved network profiles in networkmanager and recreate it, but now I have internet connection by the time Openbox is done starting up. Beautiful!

I was going to use Wicd, but I no longer trust it due to this bug mentioned in the wiki: https://wiki.archlinux.org/index.php/Wi … or_message
Where Wicd will sometimes magically stop working and get dbus errors. The only solution it to completely wipe it from your system and install it again. I had that happen to me almost immediately after installing and configuring it. Since it hasn't been updated in something like a year, I doubt the fix is on its way.

The problem with both NM and Wicd (and probably any other) is that it takes a long time (10+ seconds sometimes) to reconnect to the network after resuming from suspend, even if I haven't moved to a new network since suspending. In Windows on the same machine, it's already connected by the time you type the screen lock password (maybe 2-3 seconds). I'm not saying "OMG Windows is better, Linux sucks," just that it's unfortunate and a little frustrating when there is stuff that is clearly better in Windows-land.

Hence my frustration with network managers this week.

graysky · 2011-05-29 20:24:02

http://live.gnome.org/GnomeKeyring/Ssh

I had to add my key manually and now everything is fine.

$ ssh-add -l
The agent has no identities.

$ ssh-add
Enter passphrase for /home/facade/.ssh/id_rsa: 
Identity added: /home/facade/.ssh/id_rsa (/home/facade/.ssh/id_rsa)

EDIT: Nope... I'm wrong. I have to repeat this every time I login now! Ideas as to what has gone wrong?

Last edited by graysky (2011-05-29 20:28:01)

AugustePop · 2011-05-30 08:16:30

i had this problem before, and finally ended up in empty password default keyring.

alexcriss · 2011-06-15 15:10:45

graysky wrote:

http://live.gnome.org/GnomeKeyring/Ssh
I had to add my key manually and now everything is fine.
$ ssh-add -l
The agent has no identities.

$ ssh-add
Enter passphrase for /home/facade/.ssh/id_rsa: 
Identity added: /home/facade/.ssh/id_rsa (/home/facade/.ssh/id_rsa)
EDIT: Nope... I'm wrong. I have to repeat this every time I login now! Ideas as to what has gone wrong?

Might be OT, since I use Gnome and GDM, but this happens to me as well and annoys me to no end.

wonder · 2011-06-15 15:14:19

graysky wrote:

http://live.gnome.org/GnomeKeyring/Ssh
I had to add my key manually and now everything is fine.
$ ssh-add -l
The agent has no identities.

$ ssh-add
Enter passphrase for /home/facade/.ssh/id_rsa: 
Identity added: /home/facade/.ssh/id_rsa (/home/facade/.ssh/id_rsa)
EDIT: Nope... I'm wrong. I have to repeat this every time I login now! Ideas as to what has gone wrong?

dude, i use this all the time and i do not have to type even the passphrase. Just when it asks again expand the advance list and select to automatically unlock the key. You don't have to do anything else, like the crap from the wiki

alexcriss · 2011-06-15 15:28:48

wonder wrote:

graysky wrote:
http://live.gnome.org/GnomeKeyring/Ssh
I had to add my key manually and now everything is fine.
$ ssh-add -l
The agent has no identities.

$ ssh-add
Enter passphrase for /home/facade/.ssh/id_rsa: 
Identity added: /home/facade/.ssh/id_rsa (/home/facade/.ssh/id_rsa)
EDIT: Nope... I'm wrong. I have to repeat this every time I login now! Ideas as to what has gone wrong?
dude, i use this all the time and i do not have to type even the passphrase. Just when it asks again expand the advance list and select to automatically unlock the key. You don't have to do anything else, like the crap from the wiki

The problem is that it never asks anything. I remember it was used to popup a dialog box where you could say "Remember for future" (something similar). It doesn't do it anymore! If I type

ssh-add

I am asked to type the password in the teminal (not in a popup). Same if I try to connect to some host.

Some info:

$ pacman -Qs keyring
local/gnome-keyring 3.0.3-1 (gnome)
    GNOME Password Management daemon
local/libgnome-keyring 3.0.3-1
    GNOME keyring client library
local/python-gnomekeyring 2.32.0-6
    Python bindings for libgnome-keyring
alessandro at alessandro-thinky in ~ 
$ pacman -Qs ssh
local/libssh2 1.2.7-2
    A library implementing the SSH2 protocol as defined by Internet Drafts
local/openssh 5.8p2-8
    Free version of the SSH connectivity tools
alessandro at alessandro-thinky in ~ 
$

wonder · 2011-06-15 16:23:17

i really don't get what is the problem. just try to ssh someip and it will ask for it and allow to automatically unlock it. you don't have to start and additional agent or anything

alexcriss · 2011-06-15 17:13:38

wonder wrote:

i really don't get what is the problem. just try to ssh someip and it will ask for it and allow to automatically unlock it. you don't have to start and additional agent or anything

It does not ask anything. Here is a video https://dl.dropbox.com/s/wdoz15fsf5xoej … .webm?dl=1 (recorded through Gnome Shell recording). You can see that I ssh'ed into a remote host, typed my password, nothing happened. To ssh again I have to retype the password.

wonder · 2011-06-15 17:16:23

alexcriss wrote:

wonder wrote:
i really don't get what is the problem. just try to ssh someip and it will ask for it and allow to automatically unlock it. you don't have to start and additional agent or anything
It does not ask anything. Here is a video https://dl.dropbox.com/s/wdoz15fsf5xoej … .webm?dl=1 (recorded through Gnome Shell recording). You can see that I ssh'ed into a remote host, typed my password, nothing happened. To ssh again I have to retype the password.

paste the output of
$ ps ax | grep agent
$ env | grep -i ssh

alexcriss · 2011-06-15 17:18:47

Here it goes:

alessandro at alessandro-thinky in ~ 
$ ps ax | grep agent
 8182 ?        Ss     0:00 /usr/bin/ssh-agent -- gnome-session
 8878 pts/0    S+     0:00 grep agent
alessandro at alessandro-thinky in ~ 
$ env | grep -i ssh
SSH_AGENT_PID=8182
SSH_AUTH_SOCK=/tmp/ssh-GKPaufuc8160/agent.8160

Besides, thanks as always for having had a look into this in such a quick time! It is really appreciated

UPDATE: This is getting more wierd. I used a custom nautlius script that calls scp and ssh and I got the popup asking me the password and if I want to store it. I typed the password and checked remember for future session, logged in again and it still asks me for the ssh password.

Using seahorse now I see "unlock alessandro@alessandro-thinky key" in the default login keyring password list, but it is not unlocked on login.

Last edited by alexcriss (2011-06-15 18:03:18)

alexcriss · 2011-06-16 10:36:30

I am puzzled. As said before I have a stupid nautilus script that calls scp and ssh. I used that and was asked to store the password, fine. Nonetheless the terminal still asks me for the password. The strange thing is that if I use a simple scp nautilus script I am not asked to type a password. Usual video explaining is provided here: http://db.tt/w0gOSld

Is there anyway to know what the keyring does? There is no man page, Gnome website doesn't explain much and I found no bugs on this neither in Gnome Bugzilla or Arch's Bbg tracker

alexcriss · 2011-06-21 13:06:52

@wonder

Should I report this upstream? It seems that only gnome terminal is not able to unlock my key. If I use connect to SSH server from Nautilus I am not asked any password. Besides, I've tried with urxvt and it doesn't work as well (and I do not know if it supposed to do so).

Sorry for posting again, but I could find anything that points me in the right direction
Alessandro

alexcriss · 2011-06-22 10:15:24

Last update: It seems that I've found the culprit. I was opening the terminal by using a custom keyboard shortcut. More specifically, I went to the System-Settings -> Keyboard -> Custom Launchers (should be similar, I am on an Italian localization) and created a new one that launches gnome-terminal when pressing Ctrl-Alt-T.

Now, if I launch the terminal using the shortcut and then SSH into a remote machine I'm asked to type my password, while if I launch the terminal from the gnome-shell dash, or using Alt-F2 and type gnome-terminal I can SSH wihout typing the password.

Can anyone try to add a custom shortcut for gnome-terminal and see whether SSH works without asking a password or not before I report this upstream?

Cheers, and sorry for adding more noise!

wonder · 2011-08-14 18:39:23

ok, it happened to me after reinstalling arch but keeping my /home folder.

it happens because the username that i added on the new system had a different password and gnome-keyring automatically unlock feature only works when you have the same password as in the old system.

to make it work, change the keyring password to match system one from seahorse.

i noticed this when i tried to connect with empathy and it asked the keyring password, which was odd and didn't want to use the current system password and i tried the previous one.

graysky · 2011-08-14 18:51:10

@wonder - my pw's are insync and it still happens

wonder · 2011-08-14 19:08:21

graysky wrote:

@wonder - my pw's are insync and it still happens

try to change the keyring password even when old is the same as new

Last edited by wonder (2011-08-14 19:08:40)

graysky · 2011-08-14 19:18:34

@wonder -

<In Gnome>
1) Loaded seahorse
2) Changed PW
3) Logged out then back in
4) Tried to ssh to a host with key auth and was prompted for the damn pw in the terminal!

<In XFCE4>
Sshed into the same host with no prompts of pw.

wonder · 2011-08-14 19:36:30

well, do you start ssh-agent in .bashrc or something? or how did you do it in xfce?

Last edited by wonder (2011-08-14 19:36:50)

Arch Linux

#1 2011-05-11 20:09:59

Can we no longer unlock gnome-keyring on login if we don't use GDM?

#2 2011-05-11 20:34:36

Re: Can we no longer unlock gnome-keyring on login if we don't use GDM?

#3 2011-05-11 21:53:19

Re: Can we no longer unlock gnome-keyring on login if we don't use GDM?

#4 2011-05-11 22:35:48

Re: Can we no longer unlock gnome-keyring on login if we don't use GDM?

#5 2011-05-11 22:57:34

Re: Can we no longer unlock gnome-keyring on login if we don't use GDM?

#6 2011-05-12 09:24:23

Re: Can we no longer unlock gnome-keyring on login if we don't use GDM?

#7 2011-05-12 09:54:40

Re: Can we no longer unlock gnome-keyring on login if we don't use GDM?

#8 2011-05-12 12:11:42

Re: Can we no longer unlock gnome-keyring on login if we don't use GDM?

#9 2011-05-29 20:24:02

Re: Can we no longer unlock gnome-keyring on login if we don't use GDM?

#10 2011-05-30 08:16:30

Re: Can we no longer unlock gnome-keyring on login if we don't use GDM?

#11 2011-06-15 15:10:45

Re: Can we no longer unlock gnome-keyring on login if we don't use GDM?

#12 2011-06-15 15:14:19

Re: Can we no longer unlock gnome-keyring on login if we don't use GDM?

#13 2011-06-15 15:28:48

Re: Can we no longer unlock gnome-keyring on login if we don't use GDM?

#14 2011-06-15 16:23:17

Re: Can we no longer unlock gnome-keyring on login if we don't use GDM?

#15 2011-06-15 17:13:38

Re: Can we no longer unlock gnome-keyring on login if we don't use GDM?

#16 2011-06-15 17:16:23

Re: Can we no longer unlock gnome-keyring on login if we don't use GDM?

#17 2011-06-15 17:18:47

Re: Can we no longer unlock gnome-keyring on login if we don't use GDM?

#18 2011-06-16 10:36:30

Re: Can we no longer unlock gnome-keyring on login if we don't use GDM?

#19 2011-06-21 13:06:52

Re: Can we no longer unlock gnome-keyring on login if we don't use GDM?

#20 2011-06-22 10:15:24

Re: Can we no longer unlock gnome-keyring on login if we don't use GDM?

#21 2011-08-14 18:39:23

Re: Can we no longer unlock gnome-keyring on login if we don't use GDM?

#22 2011-08-14 18:51:10

Re: Can we no longer unlock gnome-keyring on login if we don't use GDM?

#23 2011-08-14 19:08:21

Re: Can we no longer unlock gnome-keyring on login if we don't use GDM?

#24 2011-08-14 19:18:34

Re: Can we no longer unlock gnome-keyring on login if we don't use GDM?

#25 2011-08-14 19:36:30

Re: Can we no longer unlock gnome-keyring on login if we don't use GDM?

Board footer