-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2007-11-19 at 14:51 +0100, Carlos E. R. wrote:
I have an old computer with suse 7.3 on it (the latest it can use: it is a pentium classic with 32 MB). I used the other day to ssh to my main computer (opensuse 10.3) and kill a process that had locked the keyboard). It has it's small uses.
Today I tried to ssh to it, and i can't: the ssh session stays for ever like this:
cer@nimrodel:~> ssh telperion.valinor
never asking for the password. What is going on? It worked with 10.2, I think.
I learnt that I had problems ssh-ing to any destination, but only with my current user: cer@nimrodel:~> ssh 1234@router {no response} Finally, I discovered that the culprit is ssh-agent (by looking at the environment). This works instantly: cer@nimrodel:~> SSH_AGENT_PID='' SSH_ASKPASS='' SSH_AUTH_SOCK='' ssh 1234@router 1234@router's password: -> In my current session: cer@nimrodel:~> set | grep SSH_ SSH_AGENT_PID=6701 SSH_ASKPASS=/usr/lib/ssh/x11-ssh-askpass SSH_AUTH_SOCK=/tmp/ssh-mypMH6659/agent.6659 There is such an agent running: cer@nimrodel:~> ps ax | grep 6701 6701 ? Ss 0:00 /usr/bin/ssh-agent /bin/bash /home/cer/.xinitrc 27355 pts/18 S+ 0:00 grep 6701 cer@nimrodel:~> And the files do exist: cer@nimrodel:~> ls -l /usr/lib/ssh/x11-ssh-askpass /tmp/ssh-mypMH6659/agent.6659 srw------- 1 cer users 0 2007-12-25 14:49 /tmp/ssh-mypMH6659/agent.6659 -rwxr-xr-x 1 root root 30860 2007-12-12 14:55 /usr/lib/ssh/x11-ssh-askpass But my only option to ssh is to disable the agent. If I start seahorse, preferences, it hangs (it worked previously). If I do: cer@nimrodel:~> seahorse-preferences (seahorse-preferences:1724): GConf-WARNING **: Owner of /tmp/gconfd-cer3 is not the current user ** (seahorse-preferences:1724): WARNING **: Another GPG agent may be running. Disabling cache preferences. and it doesn't display. If I look up the process list, I see: 6847 ? Ss 0:00 seahorse-agent --sm-config-prefix /seahorse-agent-xqyZu2/ --sm-client-id 11c0a8010c000119470830500000184410000 --screen 0 6848 ? Ss 0:00 /usr/bin/seahorse-agent 6849 ? Ss 0:00 seahorse-agent --sm-config-prefix /seahorse-agent-V2r6aH/ --sm-client-id 11c0a8010c000119470880700000205230004 --screen 0 Two agents with very similar PID and ID, so they were started almost simultaneously. I kill -9 the second one (PID 6849), and now seahorse-preferences does work. Under the "passphrase cache" tab I read that "no ssh caching agent is running. Cannot load secure shell keys" - which is false, ssh-agent is running. If I kill the 6848 agent, then it claims there is no agent running, but that's also false, 6847 is running. Another time I'll kill in reverse order. But now I can at last ssh - although my passwords are not cached, the shh-agent thing is useless :-( I this a bug? Have I something wrong? Is this known? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHc82BtTMYHG2NR9URAgT4AJ9IPsJThVhyTSBEmoZ9+PtbC9ZDJwCfbRbv toAahnUi0MvkzOcVacughzU= =9VYu -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-security+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-security+help@opensuse.org