-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Let me ask this question here, as elsewhere I got no answer. For some time I was unable to ssh from my computer to another old one. I thought it would be a version problem, but then I discovered I could not ssh to my own router as my normal user, but I could do su-ing to a different user first. I then discovered that this sequence works: cer@nimrodel:~> SSH_AGENT_PID='' SSH_ASKPASS='' SSH_AUTH_SOCK='' ssh 1234@router 1234@router's password: -> So there is a broken ssh agent in my system. But which one? One day I killed most of them, and from then on I can ssh sucessfully. I have three running now (after a fresh reboot and an hybernate to disk): cer@nimrodel:~> ps axu | grep agent cer 5614 0.0 0.0 2980 604 ? Ss 09:14 0:00 /usr/bin/gpg-agent --sh --daemon cer 5615 0.0 0.0 5456 700 ? Ss 09:14 0:00 /usr/bin/ssh-agent /bin/bash /home/cer/.xinitrc cer 5726 0.3 0.5 95160 5204 ? Ssl 09:14 0:39 seahorse-agent --sm-config-prefix /seahorse-agent-V2r6aH/ --sm-client-id 11c0a8010c000119470880700000205230004 --screen 0 cer 5735 0.0 0.4 86968 4168 ? Ss 09:14 0:00 seahorse-agent --sm-config-prefix /seahorse-agent-xqyZu2/ --sm-client-id 11c0a8010c000119470830500000184410000 --screen 0 cer 5757 0.0 0.3 86968 4108 ? Ss 09:14 0:00 /usr/bin/seahorse-agent cer 21030 0.0 0.0 2076 700 pts/18 R+ 12:22 0:00 grep agent cer@nimrodel:~> set | grep SSH SSH_AGENT_PID=5615 SSH_ASKPASS=/usr/lib/ssh/x11-ssh-askpass SSH_AUTH_SOCK=/tmp/ssh-cBjhK5570/agent.5570 There are at least two, possible three instances of "seahorse-agent" running, and one plain "ssh-agent". When I do "ssh 1234@router" I'm asked for the passphrases to my four "*dsa" files: cer@nimrodel:~> l .ssh/*dsa - -rw------- 1 cer users 736 2004-03-19 03:17 .ssh/cfsf_dsa - -rw------- 1 cer users 736 2004-03-24 02:26 .ssh/id_dsa - -rw------- 1 cer users 744 2004-03-19 03:19 .ssh/old_shsf_dsa - -rw------- 1 cer users 744 2004-04-24 21:41 .ssh/shsf_dsa and then I get the password prompt to the ssh session. If I try again in the same xterm, I'm asked again for the password, so it is not cached, as I assume a decent ssh agent should do. My guess is that those agents are colliding. If I exit my session and enter again, then the whole agent menagerie is broken in someother way and I'm not asked for the passphrases, and seahorse control thing claims there is another agent running - I guess some seahorse was not killed on exit. Will this work some time in the "near" future? Hint: This system was upgraded from 10.2, and more - I never install fresh. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFHfhmjtTMYHG2NR9URAjK+AJ9mSDDQWSytQu4tv+ontsEEE8MIJQCfaBNK pHvIRVUl5pNGfOlJo+fl2YQ= =89Va -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-gnome+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-gnome+help@opensuse.org