feat: test that ssh host fingerprint does not change during upgrades #3374
Labels
enhancement
New feature or request
triage
Add this label to issues that should be triaged and prioretized in the next planning call
Coming from this issue: #3370
We should on upgrade store the fingerprint of the base machine and then compare it against the upgraded one to see if they match.
IIRC the peg ssh does not check the keys when ssh-ing so we might need to change it to be able to store them or match them or whatever.
The text was updated successfully, but these errors were encountered: