On Tue, May 14, 2013 at 2:12 PM, Lucas, Brandon <Brandon.Lucas@xxxxxxxxx>wrote: > The secure log on a server I am connecting to, is showing on successful > connection as if there was a key pair set up for the "bear" user between > the servers: > > May 14 14:06:18 bearServer sshd[4199]: Accepted publickey for bear from > xx.xx.xx.xx port 54305 ssh2 > May 14 14:06:18 bearServer sshd[4199]: pam_unix(sshd:session): session > opened for user bear by (uid=0) > > .. but this key pair does not exist. If I were to look at authorized keys > on the server I connected to I see: > > ssh-rsa HASH== teddy@xxxxxxxxxxxxxxxxxxxxxx > If I'm understanding correctly, you have the "teddy" key set in "bear's" authorized_keys file, and you also have "bear" using the same "teddy" key. Use the -v flag when doing the ssh to verify what key the client is using; I think you see that it is using the "teddy" pub key which you placed in "bear's" .ssh dir. I'm currently using a key created on a long dead box to connect to the console of a VPS I have, mostly cause I'm too lasy to create a new one. Every time I log in it says using pub from "<username>@<long_dead_box>". Jared Moore -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
