5 ms·
I can't reproduce this. macOS 10.15.4, ssh'ing to a very high (5digit) port with a hostname no problems.
by 0x0 7y ago
I can't reproduce this. macOS 10.15.4, ssh'ing to a very high (5digit) port with a hostname no problems.
- jpwgarrison 7y agoSame here, 5 digits and a hostname = no problem. There must be some other factor(s) in play.
- 0xff00ffee 7y agoDitto. There's a post a few levels above where they are digging into the source of ssh, I'm following that!
- ajphdiv 7y agoI can't either, in fact all 10+ of the hosts that I routinely access have ports higher than OPs issue.
- andai 7y agoOfftopic but why are people using high port numbers? Additional security due to a nonstandard port? If so, does that go together with anything additional like port knocking? Or is it multiple hosts on the same IP, but different ports?
- cozzyd 7y agoA relatively common use case is multiple devices behind a NAT, where each port goes to a different device.
- deleted 7y ago[deleted]
- vbezhenar 7y agoSome people think that it adds to security. Some people want to reduce noise in logs.
- ajphdiv 7y agoIt's to keep my logs cleaner. It doesn't add any security value since the port is still open. I don't allow password auth. I was just always annoyed with how many times port 22 was getting hit everyday by attackers.