Linux

使用 sftp 時,chrooting 使用者會導致“連接關閉”消息

  • June 4, 2012

首先我是一個linux新手,所以請不要假設太多知識。我正在使用 CentOS 5.8(最終版)並使用 OpenSSH 版本 5.8p1。

我已經創建了一個使用者playwithbits,我正在嘗試將chroot他們添加到目錄home/nginx/domains/playwithbits/public

我在我的文件中使用以下match語句:sshd_config

Match group web-root-locked
        ChrootDirectory /home/nginx/domains/%u/public
        X11Forwarding no
        AllowTcpForwarding no
        ForceCommand /usr/libexec/openssh/sftp-server

# id playwithbits返回:uid=504(playwithbits) gid=504(playwithbits) groups=504(playwithbits),507(web-root-locked)

我已將使用者的主目錄更改為:home/nginx/domains/playwithbits/public

現在,當我嘗試與該使用者進行 sftp 連接時,我會立即收到以下消息:connection closed

有誰知道我做錯了什麼?

**編輯:**遵循@Dennis Williamson 的建議,我已在調試模式下連接(我認為……如果我錯了,請糾正我)。

通過使用將所有文件的權限直接設置為 700,我取得了一些進展chmod。現在,當我嘗試登錄時收到以下消息(仍然拒絕連接):

Connection from [My ip address] port 38737
debug1: Client protocol version 2.0; client software version OpenSSH_5.6
debug1: match: OpenSSH_5.6 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.8
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 playwithbits service ssh-connection method none
debug1: attempt 0 failures 0
debug1: user playwithbits matched group list web-root-locked at line 91
debug1: PAM: initializing for "playwithbits"
debug1: PAM: setting PAM_RHOST to [My host info]
debug1: PAM: setting PAM_TTY to "ssh"
debug1: userauth-request for user playwithbits service ssh-connection method password
debug1: attempt 1 failures 0
debug1: PAM: password authentication accepted for playwithbits
debug1: do_pam_account: called
Accepted password for playwithbits from [My ip address] port 38737 ssh2
debug1: monitor_child_preauth: playwithbits has been authenticated by privileged process
debug1: SELinux support disabled
debug1: PAM: establishing credentials
User child is on pid 3942
debug1: PAM: establishing credentials
Changed root directory to "/home/nginx/domains/playwithbits/public"
debug1: permanently_set_uid: 504/504
debug1: Entering interactive session for SSH2.
debug1: server_init_dispatch_20
debug1: server_input_channel_open: ctype session rchan 0 win 2097152 max 32768
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 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 subsystem reply 1
debug1: session_by_channel: session 0 channel 0
debug1: session_input_channel_req: session 0 req subsystem
subsystem request for sftp by user playwithbits
debug1: subsystem: cannot stat /usr/libexec/openssh/sftp-server: Permission denied
debug1: subsystem: exec() /usr/libexec/openssh/sftp-server
debug1: Forced command (config) '/usr/libexec/openssh/sftp-server'
debug1: session_new: session 0
debug1: Received SIGCHLD.
debug1: session_by_pid: pid 3943
debug1: session_exit_message: session 0 channel 0 pid 3943
debug1: session_exit_message: release channel 0
debug1: session_by_channel: session 0 channel 0
debug1: session_close_by_channel: channel 0 child 0
debug1: session_close: session 0 pid 0
debug1: channel 0: free: server-session, nchannels 1
Received disconnect from [My ip address]: 11: disconnected by user
debug1: do_cleanup
debug1: do_cleanup
debug1: PAM: cleanup
debug1: PAM: closing session
debug1: PAM: deleting credentials

從伺服器端調試時,這些問題總是更容易。我建議在調試模式下啟動第二台伺服器,使用類似/usr/sbin/sshd -p 2222 -d. 然後你可以從你的客戶端連接sftp -P 2222 user@remotehost,並期望伺服器告訴你它為什麼斷開連接。很可能存在權限問題,我的猜測是您沒有滿足主目錄由 root 擁有的要求。

如果啟動文件輸出任何文本,這可能會導致ssh連接問題,並且可能與sftp. 檢查以確保任何profilebashrc文件在/etc$HOME不輸出任何文本。

引用自:https://serverfault.com/questions/395370