Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow the use of SSH keys #205

Open
SpokeyWheeler opened this issue Aug 23, 2018 · 2 comments
Open

Allow the use of SSH keys #205

SpokeyWheeler opened this issue Aug 23, 2018 · 2 comments

Comments

@SpokeyWheeler
Copy link

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.

@mpreisler mpreisler added this to the 1.2.1 milestone Aug 29, 2018
@TryTryAgain
Copy link

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.

@jan-cerny jan-cerny removed this from the 1.2.1 milestone Jan 27, 2020
@modem7
Copy link

modem7 commented Apr 5, 2023

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants