ssh登录很慢解决方法
使用ssh客户端(如:putty)连接Linux服务器,可能会等待10-30秒才有提示输入密码。严重影响工作效率。登录很慢,登录上去后速度正常,这种情况主要有两种可能的原因:
1. DNS反向解析问题
OpenSSH在用户登录的时候会验证IP,它根据用户的IP使用反向DNS找到主机名,再使用DNS找到IP地址,最后匹配一下登录的IP是否合法。如果客户机的IP没有域名,或者DNS服务器很慢或不通,那么登录就会很花时间。
解决办法:在目标服务器上修改sshd服务器端配置,并重启sshd
- vi /etc/ssh/sshd_config
- UseDNS no
2. 关闭ssh的gssapi认证
用ssh -v user@server 可以看到登录时有如下信息:
- debug1: Next authentication method: gssapi-with-mic
- debug1: Unspecified GSS failure. Minor code may provide more information
注:ssh -vvv user@server 可以看到更细的debug信息
解决办法:
修改sshd服务器端配置
- vi /etc/ssh/ssh_config
- GSSAPIAuthentication no
可以使用ssh -o GSSAPIAuthentication=no user@server登录
GSSAPI ( Generic Security Services Application Programming Interface) 是一套类似Kerberos 5的通用网络安全系统接口。该接口是对各种不同的客户端服务器安全机制的封装,以消除安全接口的不同,降低编程难度。但该接口在目标机器无域名解析时会有 问题
使用strace查看后发现,ssh在验证完key之后,进行authentication gssapi-with-mic,此时先去连接DNS服务器,在这之后会进行其他操作
- [root@192-168-3-40 ~]# ssh -vvv root@192.168.3.44
- OpenSSH_5.3p1, OpenSSL 1.0.1e-fips 11 Feb 2013
- debug1: Reading configuration data /etc/ssh/ssh_config
- debug1: Applying options for *
- debug2: ssh_connect: needpriv 0
- debug1: Connecting to 192.168.3.44 [192.168.3.44] port 22.
- debug1: Connection established.
- debug1: permanently_set_uid: 0/0
- debug1: identity file /root/.ssh/identity type -1
- debug1: identity file /root/.ssh/identity-cert type -1
- debug1: identity file /root/.ssh/id_rsa type -1
- debug1: identity file /root/.ssh/id_rsa-cert type -1
- debug1: identity file /root/.ssh/id_dsa type -1
- debug1: identity file /root/.ssh/id_dsa-cert type -1
- debug1: identity file /root/.ssh/id_ecdsa type -1
- debug1: identity file /root/.ssh/id_ecdsa-cert type -1
- debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3
- debug1: match: OpenSSH_5.3 pat OpenSSH*
- debug1: Enabling compatibility mode for protocol 2.0
- debug1: Local version string SSH-2.0-OpenSSH_5.3
- debug2: fd 3 setting O_NONBLOCK
- debug1: SSH2_MSG_KEXINIT sent
- debug3: Wrote 960 bytes for a total of 981
- debug1: SSH2_MSG_KEXINIT received
- debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
- debug2: kex_parse_kexinit: ssh-rsa-cert-v01@openssh.com,ssh-dss-cert-v01@openssh.com,ssh-rsa-cert-v00@openssh.com,ssh-dss-cert-v00@openssh.com,ssh-rsa,ssh-dss
- debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
- debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
- debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
- debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
- debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
- debug2: kex_parse_kexinit: none,zlib@openssh.com,zlib
- debug2: kex_parse_kexinit:
- debug2: kex_parse_kexinit:
- debug2: kex_parse_kexinit: first_kex_follows 0
- debug2: kex_parse_kexinit: reserved 0
- debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1
- debug2: kex_parse_kexinit: ssh-rsa,ssh-dss
- debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
- debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
- debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
- debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
- debug2: kex_parse_kexinit: none,zlib@openssh.com
- debug2: kex_parse_kexinit: none,zlib@openssh.com
- debug2: kex_parse_kexinit:
- debug2: kex_parse_kexinit:
- debug2: kex_parse_kexinit: first_kex_follows 0
- debug2: kex_parse_kexinit: reserved 0
- debug2: mac_setup: found hmac-md5
- debug1: kex: server->client aes128-ctr hmac-md5 none
- debug2: mac_setup: found hmac-md5
- debug1: kex: client->server aes128-ctr hmac-md5 none
- debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
- debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
- debug3: Wrote 24 bytes for a total of 1005
- debug2: dh_gen_key: priv key bits set: 120/256
- debug2: bits set: 506/1024
- debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
- debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
- debug3: Wrote 144 bytes for a total of 1149
- debug3: check_host_in_hostfile: host 192.168.3.44 filename /root/.ssh/known_hosts
- debug3: check_host_in_hostfile: host 192.168.3.44 filename /root/.ssh/known_hosts
- debug3: check_host_in_hostfile: match line 8
- debug1: Host '192.168.3.44' is known and matches the RSA host key.
- debug1: Found key in /root/.ssh/known_hosts:8
- debug2: bits set: 527/1024
- debug1: ssh_rsa_verify: signature correct
- debug2: kex_derive_keys
- debug2: set_newkeys: mode 1
- debug1: SSH2_MSG_NEWKEYS sent
- debug1: expecting SSH2_MSG_NEWKEYS
- debug3: Wrote 16 bytes for a total of 1165
- debug2: set_newkeys: mode 0
- debug1: SSH2_MSG_NEWKEYS received
- debug1: SSH2_MSG_SERVICE_REQUEST sent
- debug3: Wrote 48 bytes for a total of 1213
- debug2: service_accept: ssh-userauth
- debug1: SSH2_MSG_SERVICE_ACCEPT received
- debug2: key: /root/.ssh/identity ((nil))
- debug2: key: /root/.ssh/id_rsa ((nil))
- debug2: key: /root/.ssh/id_dsa ((nil))
- debug2: key: /root/.ssh/id_ecdsa ((nil))
- debug3: Wrote 64 bytes for a total of 1277
- debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
- debug3: start over, passed a different list publickey,gssapi-keyex,gssapi-with-mic,password
- debug3: preferred gssapi-keyex,gssapi-with-mic,publickey,keyboard-interactive,password
- debug3: authmethod_lookup gssapi-keyex
- debug3: remaining preferred: gssapi-with-mic,publickey,keyboard-interactive,password
- debug3: authmethod_is_enabled gssapi-keyex
- debug1: Next authentication method: gssapi-keyex
- debug1: No valid Key exchange context
- debug2: we did not send a packet, disable method
- debug3: authmethod_lookup gssapi-with-mic
- debug3: remaining preferred: publickey,keyboard-interactive,password
- debug3: authmethod_is_enabled gssapi-with-mic
- debug1: Next authentication method: gssapi-with-mic
- debug3: Trying to reverse map address 192.168.3.44.
- debug1: Unspecified GSS failure. Minor code may provide more information
- Cannot determine realm for numeric host address
- debug1: Unspecified GSS failure. Minor code may provide more information
- Cannot determine realm for numeric host address
- debug1: Unspecified GSS failure. Minor code may provide more information
- debug1: Unspecified GSS failure. Minor code may provide more information
- Cannot determine realm for numeric host address
- debug2: we did not send a packet, disable method
- debug3: authmethod_lookup publickey
- debug3: remaining preferred: keyboard-interactive,password
- debug3: authmethod_is_enabled publickey
- debug1: Next authentication method: publickey
- debug1: Trying private key: /root/.ssh/identity
- debug3: no such identity: /root/.ssh/identity
- debug1: Trying private key: /root/.ssh/id_rsa
- debug3: no such identity: /root/.ssh/id_rsa
- debug1: Trying private key: /root/.ssh/id_dsa
- debug3: no such identity: /root/.ssh/id_dsa
- debug1: Trying private key: /root/.ssh/id_ecdsa
- debug3: no such identity: /root/.ssh/id_ecdsa
- debug2: we did not send a packet, disable method
- debug3: authmethod_lookup password
- debug3: remaining preferred: ,password
- debug3: authmethod_is_enabled password
- debug1: Next authentication method: password
- root@192.168.3.44's password:
转载于https://blog.linuxeye.com/420.html
ssh登录很慢解决方法的更多相关文章
- CentOS 7.6出现SSH登录失败的解决方法
CentOS 7.6出现SSH登录失败的解决方案 问题重现: iterm登录 ssh vagrant@192.168.10.10 The authenticity of host '192.168.1 ...
- 关于sqlserver身份登录失败的解决方法
前几天写程序需要用到数据库,下载了一个用用,出现了不少的小问题(都怪我的32bit不争气的笔记本),有问题不要怕,至少证明我们在思考解决方案.废话不说了,直接上正题. Sqlserver有两种登陆方式 ...
- [转]win7下apache2.4响应很慢解决方法
win7下apache2.4响应很慢解决方法 PS.按照以下方法测试了以下,似乎确实快了一点[skysowe] 转载自: http://blog.sina.com.cn/s/blog_75ad1010 ...
- 因修改/etc/ssh权限导致的ssh不能连接异常解决方法
因修改/etc/ssh权限导致的ssh不能连接异常解决方法 现象: $ssh XXX@192.168.5.21 出现以下问题 Read from socket failed: Connection r ...
- SSH登录很慢问题的解决
用ssh连其他linux机器,会等待10-30秒才有提示输入密码.严重影响工作效率.登录很慢,登录上去后速度正常,这种情况主要有两种可能的原因: 1. DNS反向解析的问题 OpenSSH在用户登录的 ...
- CentOS6.5 ssh远程连接缓慢解决方法
UseDNS no GSSAPIAuthentication no 1.适用命令及方案如下:[远程连接及执行命令]ssh -p22 root@10.0.0.19ssh -p22 root@10.0.0 ...
- 【转】bash: ssh: command not found解决方法(linux)
原文转自:http://www.cnblogs.com/ahauzyy/archive/2013/04/25/3043699.html 今天在搭建hadoop的开发环境中,用的是centsos6.0的 ...
- ssh登录慢的解决办法
ubuntu的ssh登录有点慢,其实是很慢 google了一把,发现可以这样解决: (1)可能是DNS反向解析的问题 对于这样的问题,可以在/etc/ssh/sshd_config 中添加/修改: U ...
- win8 下 IIS APPPOOL\DefaultAppPool 登录失败的解决方法
来源:网络 添加ASP.NET网站时,选择添加"添加应用程序"连接sql server 2005(2008)可能会报始下的错误:(说明:2005必报错,2008选报错)" ...
随机推荐
- vbox里面的Ubuntu虚拟机与主机win7之间设置共享文件夹
有时候我们希望虚拟机和主机之间进行通信,例如传一些文件.那么设置共享文件夹就是一种很好的方式. 这里我的主机是win7系统,vbox里面的虚拟机是Ubuntu. 1.首先安装vbox的VBOXGues ...
- 完全卸载mysql 停止服务、卸载相关程序、删除注册表
本节主要介绍了完全卸载mysql的具体步骤包括停止服务.卸载相关程序.删除注册表等等 1. 停止服务MySQL 2. 卸载mysql相关的程序 3. 删除注册表(运行->regedit),m ...
- bzoj 1040: [ZJOI2008]骑士 環套樹DP
1040: [ZJOI2008]骑士 Time Limit: 10 Sec Memory Limit: 162 MBSubmit: 1755 Solved: 690[Submit][Status] ...
- 详解 Android 的 Activity 组件
Activity 的生命周期 和 J2ME 的 MIDlet 一样,在 android 中,Activity 的生命周期交给系统统一管理.与 MIDlet 不同的是安装在 android 中的所有的 ...
- Node.js V0.12新特性之性能优化
v0.12悠长的开发周期(已经过去九个月了,并且还在继续,是有史以来最长的一次)让核心团队和贡献者们有充分的机会对性能做一些优化.本文会介绍其中最值得注意的几个. 支持塞住模式的可写流 现在可写流可以 ...
- win7系统VPN设置
为了解除公司上网策略限制,或者为了上Google,Facebook,都可以通过设置VPN实现. 要使用VPN需要到VPN服务商注册,链接VPN服务商. ======================== ...
- libstdc++.so.5: cannot open shared object file: No such file or directory
中文分词一般会选择ICTCLAS的模块,虽然不能说很完美,但也算是一个不错的选择.它提供了windows版本和linux版本,并支持C/C#/JNI接口.这本来是一个不错的事情,但版本一多,官方似乎就 ...
- iOS-NSString-Base64String-Base64原理
之前看到好多人找Str2Base64Str,还有好多自己写了方法的,仔细研究了下base64的编码原理(这个我写在下面),发现官方的API已经可以完成这项功能,这里贴出来供大家参考. 一言不合就上代码 ...
- 如何 对 Windows 窗体控件进行线程安全调用
//主线程 public delegate void UpdateMessage(string mes); public void UpdatePortMessage(string mes) { th ...
- Linux Eclipse代码提示功能设置(Java & C/C++)
最近在Linux下开发,由于长期使用Visual Studio 2010,对代码提示功能情有独钟,现在在Linux下,使用Eclipse做开发,当然免不了怀念Visual Studio强悍的代码提示, ...