Host key verification failed about ssh-agent HOT 3 CLOSED

Thanks for the tips!

Unfortunately the ssh-keyscan does not work for my case. However, I found a working one as follows:

- name: Reference data
      run: |
        ssh -o StrictHostKeyChecking=no username@server1
        ssh -o StrictHostKeyChecking=no -J username@server1 username@server2
        scp -o 'ProxyCommand ssh username@server1 -W %h:%p' username@server2:filename .
        cat filename

This is really tricky.

from ssh-agent.

I think this has nothing to do with this action.

My guess is that the worker node (where the GH Action is executed) does not know your host's server2 public host key to verify that server's identity.

You can use ssh-keyscan server2 to obtain that key.

At best, you gather that key, review/verify it and then make sure that your action writes/appends it to ~/.ssh/known_hosts before you run the scp command.

You could also use run ssh-keyscan server2 >> ~/.ssh/known_hosts directly in a run command in your workflow; but that would accept and trust any key that would be offered at the time the action runs – in other words, if would completely defeat the whole purpose of SSH host key checking in the first place.

from ssh-agent.

@henry2004y It's generally safer to not rely on ssh-keyscan (that equals to disabling host key verification in case of ci scripts). See a workaround here.

from ssh-agent.