panda.zhmail.com, it's a machine on the same LAN as thinkpad. I run dnscache on thinkpad, and the TTL of panda.zhmail.com is 2 days, and I put "172.16.10.32 thinkpad" in panda:/etc/hosts, so the delay was not caused by DNS resolving. Considering that the delay occured as ssh printed out the following warning message:
-----------------------------------------------------------
Configuration file does not specify default realm
debug1: An invalid name was supplied
A parameter was malformed
Validation error
debug1: An invalid name was supplied
Configuration file does not specify default realm
debug1: An invalid name was supplied
A parameter was malformed
Validation error
-----------------------------------------------------------
it must have been introduced by the "GSSAPIAuthentication yes" parameter in ssh_config. Since average users don't use Kerberos, I think the parameter should defaults to "no".
panda.zhmail.com, it's a machine on the same LAN as thinkpad. I run dnscache on thinkpad, and the TTL of panda.zhmail.com is 2 days, and I put "172.16.10.32 thinkpad" in panda:/etc/hosts, so the delay was not caused by DNS resolving. Considering that the delay occured as ssh printed out the following warning message:
------- ------- ------- ------- ------- ------- ------- ------- ---
Configuration file does not specify default realm
debug1: An invalid name was supplied
A parameter was malformed
Validation error
debug1: An invalid name was supplied
Configuration file does not specify default realm
debug1: An invalid name was supplied ------- ------- ------- ------- ------- ------- ------- ---
A parameter was malformed
Validation error
-------
it must have been introduced by the "GSSAPIAuthenti cation yes" parameter in ssh_config. Since average users don't use Kerberos, I think the parameter should defaults to "no".