Open SpokeyWheeler opened 6 years ago
I came across this issue as well. Until supplying an ssh key/path is supported within scap-workbench, you can work around this by adding explicit information in your ssh config; ie: edit ~/.ssh/config
and add the following:
Host server1.example.com
IdentityFile ~/Downloads/server1_key.pem
Host server2
IdentityFile /home/Downloads/server2.pem
And then simply entering username@server1.example.com
or username@server2
would work in the workbench and use the key you provided in the IdentityFile line for that host.
Is there any official word from the team if this will get implemented at all?
Due to the nature of our particular environment, we don't allow for plain text passwords, so having the option for SSH keys would be tremendously helpful!
Thanks for the work so far!
I am testing this and our AWS config is such that I have pass a .pem file when using ssh. I couldn't see how to do this in the workbench. I was able to download and modify the oscap-ssh script, but that didn't seem to change anything on the workbench.