公司的服务器一直是用户名+密码的方式登陆的。
我的机器前几天还能正常登陆的，最近无非就是装了一个github的客户端，还有用brew装了python3（顺带着安装了openssl，现已删除），然后就发现用：ssh username@host_ip 这种方式无法登陆远程主机了，用ssh -vvv username@host_ip的调试信息如下：
---------------------------------
Last login: Fri Jul 11 16:05:39 on ttys000
bokix-macbook:~ bokix$ ssh -vvv bea@xx.xx.xx.xx
OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011
debug1: Reading configuration data /etc/ssh_config
debug1: /etc/ssh_config line 20: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to xx.xx.xx.xx [xx.xx.xx.xx] port 22.
debug1: Connection established.
debug1: identity file /Users/bokix/.ssh/id_rsa type -1
debug1: identity file /Users/bokix/.ssh/id_rsa-cert type -1
debug1: identity file /Users/bokix/.ssh/id_dsa type -1
debug1: identity file /Users/bokix/.ssh/id_dsa-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.2
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3
debug1: match: OpenSSH_5.3 pat OpenSSH_5*
debug2: fd 3 setting O_NONBLOCK
debug3: load_hostkeys: loading entries for host "xx.xx.xx.xx" from file "/Users/bokix/.ssh/known_hosts"
debug3: load_hostkeys: found key type RSA in file /Users/bokix/.ssh/known_hosts:1
debug3: load_hostkeys: loaded 1 keys
debug3: order_hostkeyalgs: prefer hostkeyalgs: ssh-rsa-cert-v01@openssh.com,ssh-rsa-cert-v00@openssh.com,ssh-rsa
debug1: SSH2_MSG_KEXINIT sent
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-rsa-cert-v00@openssh.com,ssh-rsa,ssh-dss-cert-v01@openssh.com,ssh-dss-cert-v00@openssh.com,ssh-dss
debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-gcm@openssh.com,aes256-gcm@openssh.com,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-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc@lysator.liu.se
debug2: kex_parse_kexinit: hmac-md5-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-sha1,umac-64@openssh.com,umac-128@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-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-ripemd160-etm@openssh.com,hmac-sha1-96-etm@openssh.com,hmac-md5-96-etm@openssh.com,hmac-md5,hmac-sha1,umac-64@openssh.com,umac-128@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-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96
debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64@openssh.com,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
debug2: dh_gen_key: priv key bits set: 124/256
debug2: bits set: 503/1024
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Server host key: RSA 6e:de:16:e3:7e:30:c0:a7:7f:e1:13:ce:09:11:fc:e3
debug3: load_hostkeys: loading entries for host "xx.xx.xx.xx" from file "/Users/bokix/.ssh/known_hosts"
debug3: load_hostkeys: found key type RSA in file /Users/bokix/.ssh/known_hosts:1
debug3: load_hostkeys: loaded 1 keys
debug1: Host 'xx.xx.xx.xx' is known and matches the RSA host key.
debug1: Found key in /Users/bokix/.ssh/known_hosts:1
debug2: bits set: 516/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
debug2: set_newkeys: mode 0
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug2: key: /Users/bokix/.ssh/id_rsa (0x0),
debug2: key: /Users/bokix/.ssh/id_dsa (0x0),
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 publickey,keyboard-interactive,password
debug3: authmethod_lookup publickey
debug3: remaining preferred: keyboard-interactive,password
debug3: authmethod_is_enabled publickey
debug1: Next authentication method: publickey
debug1: Trying private key: /Users/bokix/.ssh/id_rsa
debug3: no such identity: /Users/bokix/.ssh/id_rsa: No such file or directory
debug1: Trying private key: /Users/bokix/.ssh/id_dsa
debug3: no such identity: /Users/bokix/.ssh/id_dsa: No such file or directory
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
bea@xx.xx.xx.xx's password:
debug3: packet_send2: adding 64 (len 51 padlen 13 extra_pad 64)
debug2: we sent a password packet, wait for reply
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
Permission denied, please try again.
bea@xx.xx.xx.xx's password:
bokix-macbook:~ bokix$
---------------------------------
日志中的主机ip已换成xx.xx.xx.xx，不知道有没有大神能帮忙看一下
添加评论
关注(0)
相关推荐
出现这种问题， ①首先检查用户对应的角色名，然后看路径设置是否正确，有没有相关的权限，如果这些都没问题，然后就尝试下面的操作： ②重起FTP服务，最好从服务里面重启(不能根本解决)； ③重新设置Server-U帐号和...
在尝试运行 SQL Plus 工具时，可能会遇到一个错误提示：“cannot restore segment prot after reloc: Permission denied”，这通常发生在尝试加载 Oracle 的客户端库 `libclntsh.so.11.1` 时。此错误表明系统拒绝了...
在使用手机时，有时我们可能会遇到“权限被拒绝”（Permission Denied）的问题，尤其是在尝试图案解锁时。这通常是由于安全设置、系统权限或第三方应用程序冲突导致的。以下是一些详细的解决策略： 1. **检查安全...
首先我要解释一下，很多时候出现这个问题，并不是你的文件有毛病，很可能是你代码读取的路径不对，这就要追究到代码本身。批量转化可以在json_to_dataset文件里直接运行代码实现。这个思路还要感谢我的一个师兄。...
NULL 博文链接：https://lanxing.iteye.com/blog/264088
打开终端直接输入 docker 命令时出现以下错误： Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get ...解决办法： 将非root用户加入docker组 ...
Delphi ftp 报Permission denied 问题.txt.Delphi ftp 报Permission denied 问题.txt
Permission denied： 出现的原因的是：没有权限进行读、写、创建文件、删除文件等操作。 解决方法：输入命令 sudo chmod -R 777 /工作目录， 例如：sudo chmode -R 777 /home/HDD，此时就可以在该路径下进行一系列...
2、可以使用git push origin master:master推送成功，但是使用idea直接在git选项下推送还是报Permission Denied (publickey)。 可能下面提到的解决方法不是最简单的解决办法，但是我经过亲测后，能够解决上面的问题...
在使用Nginx作为Web服务器时，遇到“Permission denied”错误是常见的问题之一。Nginx 13错误代码通常表示进程试图访问某个文件或目录，但是由于权限设置不当，无法完成操作。为了解决这个问题，首先我们需要理解...
然而，服务器在运行过程中可能会遇到各种权限问题，550 Permission denied是其中一种常见的错误提示，它意味着服务器拒绝了用户的请求，通常是因为没有足够的权限去执行操作。 首先，我们来分析一下问题现象。用户...
Permission Denied(处理方案).md
Permission Denied(解决方案).md