I thought I had a pretty decent idea, but apparently I am missing something.īy default, SSH searches for id_rsa, id_cdsa, id_ecdsa_sk, id_ed25519, id_ed25519_sk, and id_dsa files. I would also appreciate a overview on how the pub and private keys interact with the client and server. Is this correct? If so why? How do I get it to offer more keys? I know it is a problem I see intermittently, because I at home I have multiple keys without much trouble. It only offers the id_rsa key, as you can see above. When I try to connect to bender I get the following output with my verbose ssh connection debug1: SSH2_MSG_NEWKEYS sentĭebug1: Authentications that can continue: publickeyĭebug1: Next authentication method: publickeyĭebug1: Trying private key: /home/bozo/.ssh/.ssh/identityĭebug1: Trying private key: /home/bozo/.ssh/.ssh/id_rsaĭebug1: Trying private key: /home/bozo/.ssh/id_dsaĭebug1: No more authentication methods to try. The first one I have named the first key id_rsa and the second key bender. I have pasted my public key into their respective authorized_keys file. I have a couple of keys for my current user that may connect to different machines. I was wondering if anyone else has experience this. I have come across this problem a couple of times when creating build servers with keyed authentication.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |