ssh user@<ip> -o StrictHostKeyChecking=no ===> It works

But when I give option as below using API,

node.runCommand("-o StrictHostKeyChecking=no");

Command: [/usr/bin/ssh user@<ip> -o StrictHostKeyChecking=no]
Exit Code: 6

It treats the option as separate command. So command execution fails.

When I give the entire command as parameter to the API,

node.runCommand("ssh -o 'StrictHostKeyChecking no' user@<ip>

ssh user@<ip> ssh -o StrictHostKeyChecking no user@<ip>

it gives ssh error due to incorrect parameter.

Exit Code: 2

Unknown command: ssh

How can I overcome this as I do not want confirmation for my ssh command?

Hi,

this is not really a fix, but more of a workaround:
you could put the option in the users ~/.ssh/config

Evo2.

I don't know which language or environment you use, but perhaps you need to single-quote the option (to avoid it being interpreted by the shell)?

Here you didn't use the = at all. Did you try

?

I have tried the quote option, but the api is removing the quote option while execution, so command fails. Even if escaping also did not work.

Also tried with equal to option which did not work.

Adding following entries to the .ssh/config worked for me.

cat ~/.ssh/config
Host *
StrictHostKeyChecking no

Change permission to 600 for this file. Now this is working fine. Thanks to all.