Eric Martin <[EMAIL PROTECTED]> wrote:
> of course I ran eix seahorse *after* hitting reply. Teaches me not to
> reply to a message 30 seconds after getting out of bed. Ok, now onto
> helpful stuff... does /tmp/keyring-L12w0n/ssh exist?
Yes. HOWEVER:
--($:~)-- sudo lsof | grep -i tmp/keyring
lsof: WARNING: can't stat() fuse.gvfs-fuse-daemon file system /home/mike/.gvfs
Output information may be incomplete.
gnome-key 8073 mike 3u unix 0xe2fd51c0 16680
/tmp/keyring-TEj1nP/socket
gnome-key 8073 mike 13u unix 0xe2e8ee00 16783
/tmp/keyring-TEj1nP/socket
That's strange - there's nothing listening on /tmp/keyring-L12w0n and
for sure not on the ssh named pipe in that directroy.
> Does any other
> sort of ssh-agent / seahorse stuff exist in /tmp?
Yes.
--($:~)-- ls -la /tmp/keyring-* /tmp/seahorse-BnTrHX/
/tmp/keyring-L12w0n:
insgesamt 41
drwx------ 2 mike users 1024 16. Apr 07:14 .
drwxrwxrwt 20 root root 39936 16. Apr 15:50 ..
srwxr-xr-x 1 mike users 0 16. Apr 07:14 socket
srwxr-xr-x 1 mike users 0 16. Apr 07:14 socket.pkcs11
srwxr-xr-x 1 mike users 0 16. Apr 07:14 ssh
/tmp/keyring-TEj1nP:
insgesamt 41
drwx------ 2 mike users 1024 16. Apr 07:18 .
drwxrwxrwt 20 root root 39936 16. Apr 15:50 ..
srwxr-xr-x 1 mike users 0 16. Apr 07:18 socket
/tmp/seahorse-BnTrHX/:
insgesamt 41
drwx------ 2 mike users 1024 16. Apr 07:14 .
drwxrwxrwt 20 root root 39936 16. Apr 15:50 ..
srw------- 1 mike users 0 16. Apr 07:14 S.gpg-agent
> When running
> ssh-agent, I get a pipe called /tmp/ssh-[a-zA-Z0-9]/agent.$pid. After
> that I'm out of ideas.
So there are two that are out of ideas.
It seems there are two strange things:
- ssh agent env.var is pointing to the wrong directory.
- nothings reading from the ssh pipe in the wrong directory.
Strange, isn't it?
BTW: The lsof command I ran was correct, wasn't it? I'd expect
that it would've shown a command which had /tmp/keyring/L12w0n/ssh
open.
Michael
--
[email protected] mailing list
