Timeline for SSH ignoring user and login with another one
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 2, 2017 at 18:57 | comment | added | Michael - sqlbot | @RubberStamp you're correct. It would not make sense for sshd to scan all users' authorized key files. | |
| Nov 2, 2017 at 13:46 | comment | added | RubberStamp |
@guax: My experience may be a bit different because I add my private keys to the ssh-agent via ssh-add and/or via GPG's ~/.gnupg/sshcontrol/ file and associated agent. I have had no trouble using the same set of keys in many locations and even with different users on the same remote host.
|
|
| Nov 2, 2017 at 13:26 | comment | added | guax |
the ~ part of that path is important, two different users with two different authorized_keys files containing the same key, you can ssh with any string as username, but ssh will log you into one of the users with the key, disregarding what you type. So you basically cannot login with different users using the same key, basically.
|
|
| Nov 2, 2017 at 12:59 | history | answered | RubberStamp | CC BY-SA 3.0 |