Signing back into the Community for the first time? You'll need to reset your password to access your account. Find out more.
Forum Discussion
Former Member
3 years agoAbility to specify which key to use (otherwise: Too many authentication failures)
I was perplexed as to why I could not SSH into a system earlier today. It looks like ssh is simply trying all of the keys in my vault, one after another, though never getting to the one it needs befo...
Former Member
3 years agoStruggling with this.
* Generated a key pair manually (as I need to use on remote dev server as well as locally, so I need access to the cert password)
* Created 1p SSH key and imported the key (passing in the saved password as part of import)
* Added key to remote and tested working by modifying my config file to specify the key to use. Successfully logged in from OSX Terminal application (i.e. without using 1password, to confirm that the cert and password works for login to this server)
* Remove ssh config setting, so login should be via 1password. Tried ssh with 1password: Too many authentication failures. This is probably because I have too many certs in 1password
* Tried shifting most of my ssh keys out of the 1password private container so I only had 6 certs. Tried ssh login: Too many authentication failures.
* Tried instructions above on this page. Exported the public key from 1password and specified it in the config file according to instructions above. "root@domain.domain.com: Permission denied (publickey)."
* Maybe it is related to permissions, ensured permissions on the exported file are secure, tried again, same result
Host mydomain.domain.com
User root
IdentityFile /Users/rodney/.ssh/id_ed25519.pub
IdentitiesOnly yes
At this point I give up.
Can someone provide step by step (bullet proof) instructions on how to get this working please.
Rod