无密码SSH仅在调试模式下工作

时间：2015-03-16 23:42:20

标签： linux ssh

我有两台机器，用户相同，需要在它们之间做无密码ssh，我有两个用户medya和orainst

medya home是/ home / medya / orainst home是/ tools / appsw / oracle / orainst

我为他们两个设置了无密码（是的，我发誓，我虔诚地完成了所有权限）。

它适用于普通主目录（medya）中的任何用户，但不适用于orainst。

而且最奇怪的是，如果我在调试模式下运行ssh服务器，它对两个用户来说都很合适!!!

这里是作为服务启动的ssh和启动为debug

的ssh的日志

这是它失败的地方：

debug1: trying public key file /tools/appsw/oracle/orainst/.ssh/authorized_keys
debug1: Could not open authorized keys '/tools/appsw/oracle/orainst/.ssh/authorized_keys': Permission denied
debug1: restore_uid: 0/0
debug1: temporarily_use_uid: 500/500 (e=0/0)
debug1: trying public key file /tools/appsw/oracle/orainst/.ssh/authorized_keys

这是完整的日志：

[root@ip-10-16-4-114 oracle]# service sshd start

Starting sshd: debug1: sshd version OpenSSH_5.3p1
debug1: read PEM private key done: type RSA
debug1: private host key: #0 type 1 RSA
debug1: read PEM private key done: type DSA
debug1: private host key: #1 type 2 DSA
debug1: rexec_argv[0]='/usr/sbin/sshd'
debug1: rexec_argv[1]='-d'
Set /proc/self/oom_score_adj from 0 to -1000
debug1: Bind to port 22 on 0.0.0.0.
Server listening on 0.0.0.0 port 22.
debug1: Bind to port 22 on ::.
Server listening on :: port 22.
debug1: Server will not fork when running in debugging mode.
debug1: rexec start in 5 out 5 newsock 5 pipe -1 sock 8
debug1: inetd sockets after dupping: 3, 3
Connection from 10.16.4.113 port 56175
debug1: Client protocol version 2.0; client 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
debug1: permanently_set_uid: 74/74
debug1: list_hostkey_types: ssh-rsa,ssh-dss
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST received
debug1: SSH2_MSG_KEX_DH_GEX_GROUP sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_INIT
debug1: SSH2_MSG_KEX_DH_GEX_REPLY sent
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: KEX done
debug1: userauth-request for user orainst service ssh-connection method none
debug1: attempt 0 failures 0
debug1: PAM: initializing for "orainst"
debug1: PAM: setting PAM_RHOST to "10.16.4.113"
debug1: PAM: setting PAM_TTY to "ssh"
debug1: userauth-request for user orainst service ssh-connection method publickey
debug1: attempt 1 failures 0
debug1: temporarily_use_uid: 500/500 (e=0/0)
**debug1: trying public key file /tools/appsw/oracle/orainst/.ssh/authorized_keys
debug1: Could not open authorized keys '/tools/appsw/oracle/orainst/.ssh/authorized_keys': Permission denied
debug1: restore_uid: 0/0
debug1: temporarily_use_uid: 500/500 (e=0/0)
debug1: trying public key file /tools/appsw/oracle/orainst/.ssh/authorized_keys**
debug1: Could not open authorized keys '/tools/appsw/oracle/orainst/.ssh/authorized_keys': Permission denied
debug1: restore_uid: 0/0
Failed publickey for orainst from 10.16.4.113 port 56175 ssh2
Connection closed by 10.16.4.113
debug1: do_cleanup
debug1: do_cleanup
debug1: PAM: cleanup

并在调试模式下记录运行ssh服务器（当我这样做时，两个用户都可以执行无密码ssh）

[root@ip-10-16-4-114 oracle]# /usr/sbin/sshd -d -p 2222
debug1: sshd version OpenSSH_5.3p1
debug1: read PEM private key done: type RSA
debug1: private host key: #0 type 1 RSA
debug1: read PEM private key done: type DSA
debug1: private host key: #1 type 2 DSA
debug1: rexec_argv[0]='/usr/sbin/sshd'
debug1: rexec_argv[1]='-d'
debug1: rexec_argv[2]='-p'
debug1: rexec_argv[3]='2222'
Set /proc/self/oom_score_adj from 0 to -1000
debug1: Bind to port 2222 on 0.0.0.0.
Server listening on 0.0.0.0 port 2222.
debug1: Bind to port 2222 on ::.
Server listening on :: port 2222.
debug1: Server will not fork when running in debugging mode.
debug1: rexec start in 5 out 5 newsock 5 pipe -1 sock 8
debug1: inetd sockets after dupping: 3, 3
Connection from 10.16.4.113 port 47631
debug1: Client protocol version 2.0; client 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
debug1: permanently_set_uid: 74/74
debug1: list_hostkey_types: ssh-rsa,ssh-dss
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST received
debug1: SSH2_MSG_KEX_DH_GEX_GROUP sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_INIT
debug1: SSH2_MSG_KEX_DH_GEX_REPLY sent
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: KEX done
debug1: userauth-request for user orainst service ssh-connection method none
debug1: attempt 0 failures 0
debug1: PAM: initializing for "orainst"
debug1: PAM: setting PAM_RHOST to "10.16.4.113"
debug1: PAM: setting PAM_TTY to "ssh"
debug1: userauth-request for user orainst service ssh-connection method publickey
debug1: attempt 1 failures 0
debug1: temporarily_use_uid: 500/500 (e=0/0)
debug1: trying public key file /tools/appsw/oracle/orainst/.ssh/authorized_keys
debug1: fd 4 clearing O_NONBLOCK
debug1: matching key found: file /tools/appsw/oracle/orainst/.ssh/authorized_keys, line 1
Found matching RSA key: 6c:ab:f3:3b:68:c3:ed:f1:d6:ae:a5:f8:06:2f:d3:8c
debug1: restore_uid: 0/0
debug1: ssh_rsa_verify: signature correct
debug1: do_pam_account: called
Accepted publickey for orainst from 10.16.4.113 port 47631 ssh2
debug1: monitor_child_preauth: orainst has been authenticated by privileged process
debug1: temporarily_use_uid: 500/500 (e=0/0)
debug1: ssh_gssapi_storecreds: Not a GSSAPI mechanism
debug1: restore_uid: 0/0
debug1: SELinux support enabled
debug1: PAM: establishing credentials
debug1: temporarily_use_uid: 500/500 (e=0/0)
debug1: ssh_gssapi_storecreds: Not a GSSAPI mechanism
debug1: restore_uid: 0/0
User child is on pid 6171
debug1: PAM: establishing credentials
debug1: permanently_set_uid: 500/500
debug1: Entering interactive session for SSH2.
debug1: server_init_dispatch_20
debug1: server_input_channel_open: ctype session rchan 0 win 1048576 max 16384
debug1: input_session_request
debug1: channel 0: new [server-session]
debug1: session_new: session 0
debug1: session_open: channel 0
debug1: session_open: session 0: link with channel 0
debug1: server_input_channel_open: confirm session
debug1: server_input_global_request: rtype no-more-sessions@openssh.com want_reply 0
debug1: server_input_channel_req: channel 0 request pty-req reply 1
debug1: session_by_channel: session 0 channel 0
debug1: session_input_channel_req: session 0 req pty-req
debug1: Allocating pty.
debug1: session_new: session 0
debug1: session_pty_req: session 0 alloc /dev/pts/1
debug1: server_input_channel_req: channel 0 request env reply 0
debug1: session_by_channel: session 0 channel 0
debug1: session_input_channel_req: session 0 req env
debug1: server_input_channel_req: channel 0 request shell reply 1
debug1: session_by_channel: session 0 channel 0
debug1: session_input_channel_req: session 0 req shell

4 个答案:

答案 0 :(得分：3)

我认为真正的问题是.ssh文件夹路径中存在符号链接会触发权限检查。类似于SELinux要求authorized_keys文件禁止对文件进行组写访问（chmod值基本为600），它对.ssh文件夹和authorized_keys文件路径中的任何符号链接强制执行相同的规则。 / p>

我认为答案很好：https://unix.stackexchange.com/questions/152417/why-cant-i-use-public-private-key-authentication-with-ssh-on-arch-linux

答案 1 :(得分：2)

我用这个

解决了这个问题 
echo 0 > /selinux/enforce

原来selinux不喜欢我用户的主文件夹是一个符号链接。

答案 2 :(得分：0)

我也遇到了这个问题，并用以下内容修复了它：

master

这里的其他答案让我觉得它是一个SELinux问题，并且恢复文件夹及其内容的默认上下文解决了这个问题。

答案 3 :(得分：0)

我也发生了同样的事情，但是我在Windows中运行OpenSSH。由于此线程中的答案，我意识到原因可能是对authorized_keys文件的权限。登录以调试模式工作，因为该模式与对该文件具有权限的同一用户一起运行，但是OpenSSH服务与LocalSystem用户一起运行。授予用户对authorized_keys的权限可以解决此问题。

相关问题
最新问题