{"id":28531,"date":"2020-03-31T15:33:36","date_gmt":"2020-03-31T19:33:36","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=28531"},"modified":"2020-03-31T15:33:36","modified_gmt":"2020-03-31T19:33:36","slug":"macos-10-15-4-broke-ssh","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2020\/03\/31\/macos-10-15-4-broke-ssh\/","title":{"rendered":"macOS 10.15.4 Broke SSH"},"content":{"rendered":"

Tyler Hall<\/a> (tweet<\/a>, Hacker News<\/a>):<\/p>\n

The user in the Apple forums was right. At least in my case, my one server that happened to be running on a non-standard ssh<\/code> port above 8192 will not connect from Catalina 10.15.4 when using the hostname instead of the IP address.<\/p><\/blockquote>\n\n

He’s not the only one<\/a>:<\/p>\n

\/usr\/bin\/ssh in macos 10.15.4 hangs if used with the -p flag to specify an alternate port and used with a hostname. This was not present in macos 10.15.3<\/p>\n

[…]<\/p>\n

Using maximum verbosity doesn’t give any clues, and max debugging on the sshd target host shows no connection is ever initiated[…]<\/p><\/blockquote>\n\n

vgene<\/a>:<\/p>\n

I had the same problem on a MacBook after upgrading to 10.15.4. However, I wasn’t using a port number higher than 8192, the socket was 75 with a hostname. The problem was solved when I replaced the hostname with its IP or plugged in an Ethernet Cable. I tried to restart mDNSResponder and flush the dns cache and switch to a different DNS server. Nothing works so far.<\/p><\/blockquote>\n\n

Previously:<\/p>\n