Topic on Project:Support desk

I tried accessing Toolforge today and I got this warning:

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ 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 a host key has just been changed. The fingerprint for the [] key sent by the remote host is []. Please contact your system administrator. Add correct host key in [] to get rid of this message. [] Host key for login.toolforge.org has changed and you have requested strict checking. Host key verification failed.

I have removed [some information] thinking maybe it shouldn't be public. What does it mean exactly and what should my course of action be? Can someone help me?

It probably means they reinstalled the operating system. The error means that you are talking to a different computer than last time you connected. In theory it could be someone evesdropping on the connection, but in practise it usually just means toolforge was updated.

If your paranoid, check the value against those listed at https://wikitech.wikimedia.org/wiki/Help:SSH_Fingerprints/login.toolforge.org

@Bawolff, thanks a lot for the straightforward answer! What exactly should I be changing so it allows me to login in again?

This: login.toolforge.org,185.15.56.48 ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBFnJSjCGW7kli+cdgtmndPAl4xLZNc9uqP9KWlsnVDqr8yQ2RkR5ACbXe6XZ+dS09Wc9ulOmGTOwCImMi9Fho78=

To this: login.toolforge.org,185.15.56.48 ecdsa-sha2-nistp256 xxW0+dRvWgCzYOq7uBKXXo7Xze0FVezt0QikIkpeMKI= ?

That can't be right because I already tried that and I got the same message while still not being allowed to log in.

Generally i just delete the particular line from the config file (on next login it will ask if you want to trust, if you press y it will add an appropriate line back). Usually there are 2 lines you need to remove, one for the domain name and one for the ip address.

It worked and I'm now logged in. I deleted the old file as well.

Last question: In my known hosts, beside Toolforge, I also had this: [gerrit.wikimedia.org]:29418,[208.80.154.137]:29418 ssh-rsa AAAAB3Nza...+oVFf1CgQ==

What exactly is that and would I need to change anything in regard to it or does the Toolforge update not have any connection whatsoever with that?

They are separate. Gerrit is the wikimedia code review tool (which also uses ssh). If you ever used git review (or git push) on a wikimedia code base, that is where that line comes from.

I have. Again, thanks a lot for the fast and straightforward answers. My past experiences with WikiTech stuff have been frustrating and I've usually been redirected in the IRC chat channels. I saw that you were singlehandedly handling all the request here and that's to be appraised. Thank you and have a good day! :)

@Klein Muçi, Remember if you use cloud services, It's highly recommend to subscribe to at least the cloud-announce mailing list, The relevant topic for this announcement was [Cloud-Announce] [IMPORTANT] login.toolforge.org now points to Buster Grid Engine, for your first post.

@P858snake, where do I subscribe to these mailing lists?

@Klein Muçi Create a account on our Mailman install (or login, if you already have one) at https://lists.wikimedia.org/ then if you navigate to the clouds-announce mailing list and choose the subscription option.

Wow, so many possible lists! Is the "Mailman install" a new thing? I didn't have an account for it apparently but I remember doing something more old-school for subscription in the past. I created an account and indeed I had some lists I had subscripted to already. I'm very much fond of this "new way" though. I did subscribe to it. Thank you for assisting me through this!

@Klein Muçi We migrated from Mailman 2.X to 3.X last April/May which brought quite a few improvements.

Thanks for this discussion! I just had the same issue. Thank you @Bawolff for the link to the SSH fingerprints.