You are not logged in.
Hi there,
I'm new to Arch linux (coming from Ubuntu) and I'm wondering how to set up a keyring that works with that gnome-network-manager applet and ssh(fs). I previously used GNOME and the gnome keyring, and all out of the box.
I couldn't find any manuals on how to set up the gnome-keyring in Arch linux, neither regarding ssh(fs) nor network-manager. I read people are complaining about network-manager asking for the keyring-unlocking-password, but this doesn't happen for me.
How do I set up the gnome-keyring propertly?
Offline
Switch to wicd?
Offline
If I remember correctly, wicd stores passwords as plain text.
Offline
...and it wouldn't solve the ssh-problem
Offline
If I remember correctly, wicd stores passwords as plain text.
Seriously? Wow, that's a major drawback...
The day Microsoft makes a product that doesn't suck, is the day they make a vacuum cleaner.
--------------------------------------------------------------------------------------------------------------
But if they tell you that I've lost my mind, maybe it's not gone just a little hard to find...
Offline
moljac024:
https://bugs.launchpad.net/wicd/+bug/377471
Edit:
dauerbaustelle, have you seen this? http://live.gnome.org/GnomeKeyring/Ssh
Last edited by siriusb (2010-02-07 17:19:24)
Offline
siriusb, yes I have, but I can't get the keyring working at all...
Offline
Is the daemon running? Help says to
gnome-keyring-daemon --components=ssh
Just an idea, I installed cgmail which set up a keyring for me. You may want to check it out to have a keyring at all.
Last edited by siriusb (2010-02-08 08:34:06)
Offline
It seems like it isn't running, even not after I started it manually. gnome-keyring-manager keeps telling me that the daemon is not running, but I have several keyring daemon processes running (I can tell you the PID )
Neither Seahorse (that GNOME password management tool) recognizes the keyring.
Offline
You need to export the variables set by gnome-keyring-daemon.
I have this in my ~/.xinitrc:
eval $(gnome-keyring-daemon)
export GNOME_KEYRING_PID GNOME_KEYRING_SOCKET SSH_AUTH_SOCK
Offline
Thank you, that seems to work. I'll try that with networkmanager on next reboot.
Offline
From this bug page:
The /etc/wicd/wireless-settings.conf file is made root-readable only. This means that any malicious users must have root access or physical access to the machine. In either of these cases, you have far more problems than worrying about the wireless network key.
Please see http://developer.pidgin.im/wiki/PlainTextPasswords for a very good explanation as to why the passwords are not encrypted.
It may be plain text, but only root can read/write.
Offline
I wonder what that eval does in this case.
Offline
eval is a shell (bash/zsh, but it is probably present in the original Bourne shell ("sh") as well) built-in command that uses the output from a program (or command) as a command in itself.
gnome-keyring-manager prints the needed environment variables on the standard output, and when you use eval in the way I described above, these variables are set (i.e. the variable GNOME_KEYRING_SOCKET is to its correct value). The second line I used exports these variables so they are available to all subsequent applications (including shells), so that they are aware of it.
Offline
starting the ck-launch-session before ${yourde}-session helps a lot with things like this...
"Till shade is gone, till water is gone, into the Shadow with teeth bared, screaming defiance with the last breath, to spit in Sightblinder's eye on the Last Day"
Offline
hw-tph, thanks for the information!
Zeqadious, too bad I'm not having any DE running...
Offline