Typically, you use the SSH client option -i if your key is in an
unexpected location, or if it has an unexpected filename:
See e.g.
https://stackoverflow.com/questions/84096/setting-the-default-ssh-key-location
where this is discussed.
Linux distributions often come up with an ssh agent, which can be
configured to read the key once (typically after you sign in), and then
use it multiple times without a prompt. So I would say that you need to
add your private key to the agent, which is also described in the
stackoverflow question, and then it should work without further issues.
On 26. 08. 20 0:22, Matt O'Hare wrote:
Hello,
I'm new to Linux and open scap so please bear with me.
I'm trying to use scap workbench to run a scan on a remote server,
however, the remote server requires a private key for authentication.
I am able to ssh into the server using the following command: ssh -i
<private key> server@ip-address. When I run scap workbench against the
server it gives an authentication failure message.
Is there a way to make this work? Any help would be greatly appreciated.
Matt
_______________________________________________
Open-scap-list mailing list
Open-scap-list@redhat.com
https://www.redhat.com/mailman/listinfo/open-scap-list
_______________________________________________
Open-scap-list mailing list
Open-scap-list@redhat.com
https://www.redhat.com/mailman/listinfo/open-scap-list
