| 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 <2023> 2024 2025 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 <2023> 2024 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: GitHub's new rsa ssh host-key |
| From: | Michael Davidsaver via Tech-talk <tech-talk at aps.anl.gov> |
| To: | Andrew Johnson <anj at anl.gov>, Torsten Bögershausen <Torsten.Bogershausen at ess.eu> |
| Cc: | EPICS Tech-talk <tech-talk at aps.anl.gov> |
| Date: | Fri, 24 Mar 2023 09:59:48 -0700 |
On 3/24/23 09:15, Andrew Johnson via Tech-talk wrote:
Hi Torsten, On 3/24/23 10:07 AM, Torsten Bögershausen wrote:I stumbled accross the same problem today.I had over 100 emails in my inbox from our Jenkins CI-system about failing jobs because of this...Why do you have 20 IP addresses ? Shouldn't there simply be a hostname ?That may be due to an architecture change on their side. In the past the github.com DNS entry had multiple IP addresses and the actual SSH server you talked to was picked at random from that list. Now it looks like there is only one IP address, and it's in a different range than the older addresses that appear in my known_hosts files. I'm deleting all of those other entries.
The view for me:
$ dig +noall +answer github.com github.com. 31 IN A 192.30.255.113> $ dig +noall +answer -x 192.30.255.113 113.255.30.192.in-addr.arpa. 3419 IN PTR lb-192-30-255-113-sea.github.com.
I guess "lb-" abbreviates Load Balance. It looks like my known_hosts file was hashed at some point, which complicates cleaning out all of these IP entries in one go.