3 ms·
I suspect this is due to a feature being enabled for canonicalization and that the key part is the presence of the colon rather than the port number. On a 10.15
by acdha 7y ago
I suspect this is due to a feature being enabled for canonicalization and that the key part is the presence of the colon rather than the port number. On a 10.15.4 system, I see a line in the debug output which is not present in the screenshot:
> debug1: resolve_canonicalize: hostname example.org:7999 is an unrecognised address
If instead I use `-p` or a config-file option, everything works as expected.
- lilyball 7y agohostname:port is not a valid destination according to ssh syntax. A destination may either be [user@]hostname or a URI of the form ssh://[user@]hostname[:port].
- richardkmichael 7y agoThe Apple forum article cites by the OP indicates it's a problem with `-p <PORT>` as well. https://discussions.apple.com/thread/251226509 https://discussions.apple.com/thread/251226509
- jki275 7y agoThat's a fair point. I use either a ssh config file with all the correct options in it, or the -p option if I'm doing it without a config file, perhaps that's why I've never had a problem.