Question

我正在尝试为PCI合规性制定一些chrooting。我想一些用户只能通过sftp连接而不是ftp（我可以很容易地限制）。但是我需要对sftp用户进行chroot，以便他们可以遍历dir树并查看所有内容。

我将此添加到我的openssh ssd_config文件中，首先测试一个用户：

Match User dbl
ChrootDirectory %h
AllowTCPForwarding no
X11Forwarding no
ForceCommand internal-sftp

当我尝试连接时，我得到了这个输出：

$ sftp -v dbl@hostname
OpenSSH_5.9p1, OpenSSL 0.9.8x 10 May 2012
debug1: Reading configuration data /etc/ssh_config
debug1: /etc/ssh_config line 20: Applying options for *
debug1: /etc/ssh_config line 53: Applying options for *
debug1: Connecting to hostname [x.x.x.x] port 22.
debug1: Connection established.
debug1: identity file /Users/me/.ssh/id_rsa type 1
debug1: identity file /Users/me/.ssh/id_rsa-cert type -1
debug1: identity file /Users/me/.ssh/id_dsa type -1
debug1: identity file /Users/me/.ssh/id_dsa-cert type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.2p2-hpn13v14 FreeBSD-openssh-portable-6.2.p2_2,1
debug1: match: OpenSSH_6.2p2-hpn13v14 FreeBSD-openssh-portable-6.2.p2_2,1 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.9
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
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
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Server host key: RSA 54:8b:66:39:15:d4:6f:ed:82:d4:c2:82:b0:a3:45:03
debug1: Host 'hostname' is known and matches the RSA host key.
debug1: Found key in /Users/me/.ssh/known_hosts:35
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: Roaming not allowed by server
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /Users/me/.ssh/id_rsa
debug1: Authentications that can continue: publickey,password
debug1: Trying private key: /Users/me/.ssh/id_dsa
debug1: Next authentication method: password
dbl@hostname's password:
debug1: Authentication succeeded (password).
Authenticated to hostname ([x.x.x.x]:22).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: channel 0: free: client-session, nchannels 1
debug1: fd 0 clearing O_NONBLOCK
Connection to hostname closed by remote host.
Transferred: sent 1920, received 2560 bytes, in 0.0 seconds
Bytes per second: sent 1111840.9, received 1482454.5
debug1: Exit status -1
Connection closed

正如您所看到的，在我输入密码之后，我就可以立即关闭连接。它甚至没有提出像它应该的sftp提示。我在这里尝试过其他一些看似相关的帖子但是没有得到任何地方。

每个用户都有/ bin / sh作为他们的shell。

Answer 1

我过去曾经看到过一些与SFTP类似的问题，而且大部分时间都是通过在sshd_config中添加缺少的顶线来解决的。

Subsystem     sftp     internal-sftp
Match Group sftponly
    ChrootDirectory /home/%u
    ForceCommand internal-sftp
    AllowTcpForwarding no

此外，如果您计划添加更多用户，可能最好设置一个像我的配置一样的sftp组。

我把博客文章稍微提了回来，但是对于openssh-5而言。还包含一个脏但有效的交互式脚本，可以在几秒钟内设置新用户。当新客户端加入时，可以随时使用它。

http://264nmtechblog.wordpress.com/2013/10/

希望这是一些帮助 - 如果没有，可能会发布您的/ var / log / secure，如果您的问题是基于权限的话，可能会让您更好地提醒。

chroot没有在openssh 6.2上工作

1 个答案: