-
Type:
Bug
-
Resolution: Cannot Reproduce
-
Priority:
Medium
-
None
-
Affects Version/s: 2.10.1
-
Component/s: Installation, SSH
-
None
Whenever Stash is upgraded following instructions, I get the classic RSA fingerprint has changed error:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that the RSA host key has just been changed. The fingerprint for the RSA key sent by the remote host is 13:c9:f6:9d:c1:67:16:95:69:27:08:4a:c9:16:62:75. Please contact your system administrator. Add correct host key in /home/USER/.ssh/known_hosts to get rid of this message. Offending key in /home/USER/.ssh/known_hosts:1 RSA host key for stash.customer.com has changed and you have requested strict checking. Host key verification failed. fatal: The remote end hung up unexpectedly
This means that every time I upgrade Stash I have to go and rewrite that identification in known_hosts on all developer machines and continuous integration build slaves.
It would be very useful if I could somehow keep the same fingerprint from before. This does not have to be the default behavior.
If this is already possible, consider documenting this in the upgrade guide