Não tenho certeza se isso é possível ou não. Estou executando um Ubuntu Server 11.10 e configurei um repositório Subversion em / home / svn e tenho uma pasta sftp em / home / ftp.
Meus usuários podem acessar cada multa do lado do cliente usando chaves ssh. Descobri que, ao usar o cliente ftp, eles podiam navegar pelo servidor inteiro, então eu adicionei essas linhas ao meu arquivo sshd_config para que meus usuários fossem presos na pasta ftp.
Match group workers
ChrootDirectory /home/ftp
X11Forwarding no
AllowTcpForwarding no
ForceCommand internal-sftp
O problema é que eles não podem acessar o repositório do subversion. Existe alguma maneira de conseguir algo assim trabalhando?
Obrigado.
Aqui está o arquivo sshd_config
# Package generated configuration file
# See the sshd_config(5) manpage for details
# What ports, IPs and protocols we listen for
Port 22
# Use these options to restrict which interfaces/protocols sshd will bind to
#ListenAddress ::
#ListenAddress 0.0.0.0
Protocol 2
# HostKeys for protocol version 2
HostKey /etc/ssh/ssh_host_rsa_key
HostKey /etc/ssh/ssh_host_dsa_key
HostKey /etc/ssh/ssh_host_ecdsa_key
#Privilege Separation is turned on for security
UsePrivilegeSeparation yes
# Lifetime and size of ephemeral version 1 server key
KeyRegenerationInterval 3600
ServerKeyBits 768
# Logging
SyslogFacility AUTH
LogLevel INFO
# Authentication:
LoginGraceTime 120
PermitRootLogin no
StrictModes yes
AllowGroups sshlogin
RSAAuthentication yes
PubkeyAuthentication yes
AuthorizedKeysFile /home/.ssh/%u/authorized_keys
# Don't read the user's ~/.rhosts and ~/.shosts files
IgnoreRhosts yes
# For this to work you will also need host keys in /etc/ssh_known_hosts
RhostsRSAAuthentication no
# similar for protocol version 2
HostbasedAuthentication no
# Uncomment if you don't trust ~/.ssh/known_hosts for RhostsRSAAuthentication
#IgnoreUserKnownHosts yes
# To enable empty passwords, change to yes (NOT RECOMMENDED)
PermitEmptyPasswords no
# Change to yes to enable challenge-response passwords (beware issues with
# some PAM modules and threads)
ChallengeResponseAuthentication no
# Change to no to disable tunnelled clear text passwords
PasswordAuthentication no
# Kerberos options
#KerberosAuthentication no
#KerberosGetAFSToken no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes
X11Forwarding yes
X11DisplayOffset 10
PrintMotd no
PrintLastLog yes
TCPKeepAlive yes
#UseLogin no
#MaxStartups 10:30:60
Banner /etc/issue.net
# Allow client to pass locale environment variables
AcceptEnv LANG LC_*
#Subsystem sftp /usr/lib/openssh/sftp-server -u 0022
# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the ChallengeResponseAuthentication and
# PasswordAuthentication. Depending on your PAM configuration,
# PAM authentication via ChallengeResponseAuthentication may bypass
# the setting of "PermitRootLogin without-password".
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and ChallengeResponseAuthentication to 'no'.
UsePAM no
Subsystem sftp internal-sftp -u 0022
Match group workers
ChrootDirectory /home/ftp
X11Forwarding no
AllowTcpForwarding no
ForceCommand internal-sftp
Isso porque você fez o chroot do usuário do sftp para / home / ftp, então a pasta raiz (/) estará nessa pasta e todos os arquivos / pastas dentro dela estarão disponíveis.
O problema é que / home / svn está no mesmo nível / home / ftp e não pode ser alcançado. Para torná-lo acessível pelos usuários, você pode criar sua pasta svn como subpasta / home / ftp. Ou você pode tentar ligar a pasta svn como uma subpasta de / home / ftp com:
mount -o bind /sourcefolder /destinationfolder/
Tags ubuntu