Step one: Remove the old key from your known hosts file. ![]() Detailed instructions are available below.The next time you make an SSH connection to your repository, verify that the host key fingerprint matches the fingerprint for our GitHub Enterprise host keys.There might be 2 entries in the known_hosts file: one for and one for 18.9.44.24.To resolve the warning, remove the entry for from your known_hosts file.When IS&T updates the SSH Host Keys, MIT users will see a warning of a man-in-the-middle-attack.At 3pm this afternoon, IS&T updated the SSH Host Keys. ![]() IS&T has updated our GitHub Enterprise to the latest version to address this risk. ![]() Update your Known_Hosts file to access MIT GitHub Enterpriseįriday, September 23, 2016: A CRITICAL issue has been identified for all 2.x versions of GitHub Enterprise.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |