On Thursday, February 7, 2019 at 1:04:07 PM UTC, Marcus Linsner wrote: > On Thursday, February 7, 2019 at 12:57:39 PM UTC, Marcus Linsner wrote: > > Sometimes github.com resolves to 192.30.253.112 and .113 and today(at > > least) they don't allow port 22 ssh, so `git push` fails like > > ssh: connect to host github.com port 22: No route to host > > > > I noticed however that when it resolves to something like 140.82.112.40 > > (unsure exactly the IP) then ssh works and `git push` succeeds! > > the working IP is 140.82.118.3
grreat, now not even that IP works anymore: ssh: connect to host github.com port 22: No route to host i'm guessing some epic sshd bug is being exploited? :D silly speculation(s) -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b76d8eaa-1aa2-4c18-af8c-65e74960386c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
