I even get the little notification from keepass that a key was used in another application. But I haven't messed with that yet.īut as long as its a single key loaded in, I can open a terminal and type ssh and it connects. I assume this is because there is no way ssh knows what key is associated with what IP. So if you loaded a whole bunch of keys and wanted it to use the last key in the list, the server at the end would deny you because you tried to use all the other keys in the list first.
The big caveat here is that ssh isn't smart about the keys that it has loaded. I'm pretty sure ssh-agent is started automatically on boot (pretty sure I did that by accident), which is handling the keys for openssh. I first edited the keeagent options as follows:Įxport SSH_AUTH_SOCK="/home/$USER/.ssh-keeagent.sock" I have keepass2 (2.44) with keeagent plugin installed. I am on ubuntu 20.04 with KDE plasma as desktop. So, is there a way I can run a command like this: ssh -i KEEPASS-DB-PRIVKEY or is that just not a capability of keepass/keeagent/sshagent? All the information I find online is walking through steps way above me or options that don't use the terminal. I've been trying to look into using ssh-agent, but I have actually no idea what I am doing there or how that operates. What I want to do is open my keepass database, run my existing bash script and be able to bring up an ssh session that way. I have since put all my ssh private keys in my keepass database and I am trying to figure out how to integrate keepass/keeagent with the bash terminal.īut I think I have misunderstood what keepass can actually do. The end goal here is to make a centrally available database of both passwords and private keys to utilize across different devices. Before I had a bash script with a simple menu that would just use ssh -i and get the priv key file locally from the. I found out about storing ssh private keys (of which I have a lot of) in my keepass database.
0 kommentar(er)
