Why is SSH finding remote keys for other accounts?
Posted
by
Brian Pontarelli
on Super User
See other posts from Super User
or by Brian Pontarelli
Published on 2011-11-11T15:39:38Z
Indexed on
2011/11/12
9:59 UTC
Read the original article
Hit count: 352
This is a strange issue I'm having with SSH from my Macbook Pro to a Linux (Ubuntu 11.10) server. I have a DSA key setup on the remote Linux server under my home directory like this:
/home/me/.ssh/authorzied_keys
I also have the same DSA key setup for a few other accounts on the machine named "foo" and "bar". I can log into all of the accounts fine without any password. Therefore, the DSA keys are all setup correctly.
The strange behavior I'm seeing is when debugging the SSH connection. During the connection, the SSH debug is outputting this:
debug2: key: /Users/me/.ssh/id_dsa (0x7f91a1424220)
debug2: key: /home/foo/.ssh/id_dsa (0x7f91a1425620)
debug2: key: /home/bar/.ssh/id_rsa (0x7f91a1425c60)
debug2: key: /Users/me/.ssh/id_rsa (0x0)
- This is strange for so many reasons, but essentially, why is SSH listing out keys on the server (/home/foo/.ssh/id_dsa and /home/bar/.ssh/id_rsa)?
- These files don't even exist on the server, so why are they listed?
- I'm not logging into the "foo" or "bar" accounts, so why is SSH even listing those?
- On my Macbook Pro, I only have a DSA key, but SSH is listing out an RSA key, what's that all about?
- Another user on the server doesn't get any of these messages when they log in and they have the exact same setup for their DSA key and the exact same Macbook Pro setup as mine?
Does anyone know what these messages are and why SSH is outputting them?
© Super User or respective owner