Skip to content

Force update of SSH key fingerprint at each connection #6

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

Closed
derkling opened this issue Nov 26, 2015 · 1 comment
Closed

Force update of SSH key fingerprint at each connection #6

derkling opened this issue Nov 26, 2015 · 1 comment

Comments

@derkling
Copy link
Contributor

If a target is restarted after a new rootfs has been flashed, the SSH key fingerprint check fails and this abort the connection. Since a testing target is something we trust in general, we should find a suitable workaround for that annoying issue.

Since we are using directly SSH, but instead the pxssh provided wrapper, this could be a bit more tricky.
One possible solution is to always remove the current key for the host:

ssh-keygen -R <HOST_IP>

and than send back a "yes" to accept the offered key at the prompt generated for the first connection.

Other approaches are resumed here:
http://linuxcommando.blogspot.co.uk/2008/10/how-to-disable-ssh-host-key-checking.html

@marcbonnici
Copy link
Collaborator

This should now be possible using the new implementation in #450.
If this is not the case please re-open the issue.

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

No branches or pull requests

2 participants