после меняем владельца com диры. chown root:wheel /var/www/com
не догоняю wheel тут к чему?
сделал chown root:com /var/www/com все равно не пускает
сейчас конфиги
ssh_config
после меняем владельца com диры. chown root:wheel /var/www/com
не догоняю wheel тут к чему?
сделал chown root:com /var/www/com все равно не пускает
сейчас конфиги
ssh_config
# This is the ssh client system-wide configuration file. See # ssh_config(5) for more information. This file provides defaults for # users, and the values can be changed in per-user configuration files # or on the command line.
# Configuration data is parsed as follows: # 1. command line options # 2. user-specific file # 3. system-wide file # Any configuration value is only changed the first time it is set. # Thus, host-specific definitions should be at the beginning of the # configuration file, and defaults at the end.
# Site-wide defaults for some commonly used options. For a comprehensive # list of available options, their meanings and defaults, please see the # ssh_config(5) man page.
Host * # ForwardAgent no # ForwardX11 no # ForwardX11Trusted yes # RhostsRSAAuthentication no # RSAAuthentication yes # PasswordAuthentication yes # HostbasedAuthentication no # GSSAPIAuthentication no # GSSAPIDelegateCredentials no # GSSAPIKeyExchange no # GSSAPITrustDNS no # BatchMode no # CheckHostIP yes # AddressFamily any # ConnectTimeout 0 # StrictHostKeyChecking ask # IdentityFile ~/.ssh/identity # IdentityFile ~/.ssh/id_rsa # IdentityFile ~/.ssh/id_dsa # Port 22 # Protocol 2,1 # Cipher 3des # Ciphers aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc # MACs hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160 # EscapeChar ~ # Tunnel no # TunnelDevice any:any # PermitLocalCommand no # VisualHostKey no # ProxyCommand ssh -q -W %h:%p gateway.example.com # RekeyLimit 1G 1h SendEnv LANG LC_* HashKnownHosts no GSSAPIAuthentication yes GSSAPIDelegateCredentials no
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 HostKey /etc/ssh/ssh_host_ed25519_key #Privilege Separation is turned on for security UsePrivilegeSeparation yes
# Lifetime and size of ephemeral version 1 server key KeyRegenerationInterval 3600 ServerKeyBits 1024
# 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 yes
# 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
# 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 yes
Match User com X11Forwarding no AllowTcpForwarding no ForceCommand internal-sftp ChrootDirectory /var/www/com
Мне нужен sftp доступ в нужную диреткорию для отдельного юзера и чтобы он выше не мог лазить.
Создал юзера, в файле passwd сейчас запись такая
com:x:1000:1000::/var/www/com:/bin/bash
В файле sshd_config в конец добавляю
Subsystem sftp internal-sftp
Match User com X11Forwarding no AllowTcpForwarding no ForceCommand internal-sftp ChrootDirectory /var/www/com
В итоге у всех отрубает доступ. Благо в путти ссесию не закрывает и я откатываю обратно.
убираю строку
Subsystem sftp internal-sftp
У рута доступ появляется, у com нет
В общем не знаю как дальше пробовать...
---------- Добавлено 10.08.2017 в 20:23 ----------
лог при попытке зайти от com
Aug 10 20:22:11 nginx sshd[13818]: Connection closed by 130.206.99.99 [preauth] Aug 10 20:22:13 nginx CRON[13770]: pam_unix(cron:session): session closed for user root Aug 10 20:22:16 nginx sshd[13820]: reverse mapping checking getaddrinfo for 79-0055-18.dyn.broadband.iskratelecom.ru [79.00.55.18] failed - POSSIBLE BREAK-IN ATTEMPT! Aug 10 20:22:16 nginx sshd[13820]: Accepted password for com from 79.00.55.18 port 39774 ssh2 Aug 10 20:22:16 nginx sshd[13820]: pam_unix(sshd:session): session opened for user com by (uid=0) Aug 10 20:22:16 nginx systemd: pam_unix(systemd-user:session): session opened for user com by (uid=0) Aug 10 20:22:16 nginx systemd-logind[628]: New session 1493252 of user com. Aug 10 20:22:16 nginx sshd[13825]: fatal: bad ownership or modes for chroot directory component "/var/www/" Aug 10 20:22:16 nginx sshd[13820]: pam_unix(sshd:session): session closed for user com Aug 10 20:22:16 nginx systemd-logind[628]: Removed session 1493252. Aug 10 20:22:16 nginx systemd: pam_unix(systemd-user:session): session closed for user com Aug 10 20:22:22 nginx sshd[13832]: reverse mapping checking getaddrinfo for 79-0055-18.dyn.broadband.iskratelecom.ru [79.00.55.18] failed - POSSIBLE BREAK-IN ATTEMPT! Aug 10 20:22:22 nginx sshd[13832]: Accepted password for com from 79.00.55.18 port 39775 ssh2 Aug 10 20:22:22 nginx sshd[13832]: pam_unix(sshd:session): session opened for user com by (uid=0) Aug 10 20:22:22 nginx systemd-logind[628]: New session 1493253 of user com. Aug 10 20:22:22 nginx systemd: pam_unix(systemd-user:session): session opened for user com by (uid=0) Aug 10 20:22:22 nginx sshd[13837]: fatal: bad ownership or modes for chroot directory component "/var/www/" Aug 10 20:22:22 nginx sshd[13832]: pam_unix(sshd:session): session closed for user com Aug 10 20:22:22 nginx systemd-logind[628]: Removed session 1493253. Aug 10 20:22:22 nginx systemd: pam_unix(systemd-user:session): session closed for user com
---------- Добавлено 10.08.2017 в 20:25 ----------
# 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 HostKey /etc/ssh/ssh_host_ed25519_key #Privilege Separation is turned on for security UsePrivilegeSeparation yes
# Lifetime and size of ephemeral version 1 server key KeyRegenerationInterval 3600 ServerKeyBits 1024
# 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 yes
# 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
# 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 yes
---------- Добавлено 10.08.2017 в 14:28 ----------
ааа так я не втот файл все добавлял :)))
---------- Добавлено 10.08.2017 в 15:27 ----------
Теперь такая беда
прописываю в конец файла sshd_config
#sftp-server
Subsystem sftp internal-sftp
Match User com
X11Forwarding no
AllowTcpForwarding no
ForceCommand internal-sftp
ChrootDirectory /var/www/com
перезапускаю сервис и уменя вырубает ssh у всех в том числе и у рута. Слава богу ссесию не закрывает и можно откатить изменения.
baas: Укажи настройки в этом файле /etc/ssh/sshd_config
ну выше ведь добавил
# This is the ssh client system-wide configuration file. See
# ssh_config(5) for more information. This file provides defaults for
# users, and the values can be changed in per-user configuration files
# or on the command line.
# Configuration data is parsed as follows:
# 1. command line options
# 2. user-specific file
# 3. system-wide file
# Any configuration value is only changed the first time it is set.
# Thus, host-specific definitions should be at the beginning of the
# configuration file, and defaults at the end.
# Site-wide defaults for some commonly used options. For a comprehensive
# list of available options, their meanings and defaults, please see the
# ssh_config(5) man page.
Host *
# ForwardAgent no
# ForwardX11 no
# ForwardX11Trusted yes
# RhostsRSAAuthentication no
# RSAAuthentication yes
# PasswordAuthentication yes
# HostbasedAuthentication no
# GSSAPIAuthentication no
# GSSAPIDelegateCredentials no
# GSSAPIKeyExchange no
# GSSAPITrustDNS no
# BatchMode no
# CheckHostIP yes
# AddressFamily any
# ConnectTimeout 0
# StrictHostKeyChecking ask
# IdentityFile ~/.ssh/identity
# IdentityFile ~/.ssh/id_rsa
# IdentityFile ~/.ssh/id_dsa
# Port 22
# Protocol 2,1
# Cipher 3des
# Ciphers aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc
# MACs hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160
# EscapeChar ~
# Tunnel no
# TunnelDevice any:any
# PermitLocalCommand no
# VisualHostKey no
# ProxyCommand ssh -q -W %h:%p gateway.example.com
# RekeyLimit 1G 1h
SendEnv LANG LC_*
HashKnownHosts no
GSSAPIAuthentication yes
GSSAPIDelegateCredentials no
DenyGroups com
Subsystem sftp internal-sftp
Match User com
X11Forwarding no
AllowTcpForwarding no
AllowAgentForwarding no
ermitTunnel no
ForceCommand internal-sftp
ChrootDirectory /var/www/com
chown root:wheel /var/www/com
не догоняю wheel тут к чему?
сделал chown root:com /var/www/com все равно не пускает
сейчас конфиги
ssh_config
chown root:wheel /var/www/com
не догоняю wheel тут к чему?
сделал chown root:com /var/www/com все равно не пускает
сейчас конфиги
ssh_config
# This is the ssh client system-wide configuration file. See
# ssh_config(5) for more information. This file provides defaults for
# users, and the values can be changed in per-user configuration files
# or on the command line.
# Configuration data is parsed as follows:
# 1. command line options
# 2. user-specific file
# 3. system-wide file
# Any configuration value is only changed the first time it is set.
# Thus, host-specific definitions should be at the beginning of the
# configuration file, and defaults at the end.
# Site-wide defaults for some commonly used options. For a comprehensive
# list of available options, their meanings and defaults, please see the
# ssh_config(5) man page.
Host *
# ForwardAgent no
# ForwardX11 no
# ForwardX11Trusted yes
# RhostsRSAAuthentication no
# RSAAuthentication yes
# PasswordAuthentication yes
# HostbasedAuthentication no
# GSSAPIAuthentication no
# GSSAPIDelegateCredentials no
# GSSAPIKeyExchange no
# GSSAPITrustDNS no
# BatchMode no
# CheckHostIP yes
# AddressFamily any
# ConnectTimeout 0
# StrictHostKeyChecking ask
# IdentityFile ~/.ssh/identity
# IdentityFile ~/.ssh/id_rsa
# IdentityFile ~/.ssh/id_dsa
# Port 22
# Protocol 2,1
# Cipher 3des
# Ciphers aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc
# MACs hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160
# EscapeChar ~
# Tunnel no
# TunnelDevice any:any
# PermitLocalCommand no
# VisualHostKey no
# ProxyCommand ssh -q -W %h:%p gateway.example.com
# RekeyLimit 1G 1h
SendEnv LANG LC_*
HashKnownHosts no
GSSAPIAuthentication yes
GSSAPIDelegateCredentials no
sshd_config
# 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
HostKey /etc/ssh/ssh_host_ed25519_key
#Privilege Separation is turned on for security
UsePrivilegeSeparation yes
# Lifetime and size of ephemeral version 1 server key
KeyRegenerationInterval 3600
ServerKeyBits 1024
# Logging
SyslogFacility AUTH
LogLevel INFO
# Authentication:
LoginGraceTime 120
PermitRootLogin yes
StrictModes yes
RSAAuthentication yes
PubkeyAuthentication yes
#AuthorizedKeysFile %h/.ssh/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 yes
# 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
# 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 yes
Match User com
X11Forwarding no
AllowTcpForwarding no
ForceCommand internal-sftp
ChrootDirectory /var/www/com
когда сделал рут рут на /var/www
то теперь ругается так
Из вашего объяснения я не понял своей ошибки - все тоже пробовла и я..
права root root на /var/www тоже сделал (не рекурсивно) - не помогло
права на /var/www/com ообще делал разные - тоже без эффекта
Так давайте еще раз..... Дебиан 8 панели нет
Мне нужен sftp доступ в нужную диреткорию для отдельного юзера и чтобы он выше не мог лазить.
Создал юзера, в файле passwd сейчас запись такая
В файле sshd_config в конец добавляю
Match User com
X11Forwarding no
AllowTcpForwarding no
ForceCommand internal-sftp
ChrootDirectory /var/www/com
В итоге у всех отрубает доступ. Благо в путти ссесию не закрывает и я откатываю обратно.
убираю строку
У рута доступ появляется, у com нет
В общем не знаю как дальше пробовать...
---------- Добавлено 10.08.2017 в 20:23 ----------
лог при попытке зайти от com
Aug 10 20:22:13 nginx CRON[13770]: pam_unix(cron:session): session closed for user root
Aug 10 20:22:16 nginx sshd[13820]: reverse mapping checking getaddrinfo for 79-0055-18.dyn.broadband.iskratelecom.ru [79.00.55.18] failed - POSSIBLE BREAK-IN ATTEMPT!
Aug 10 20:22:16 nginx sshd[13820]: Accepted password for com from 79.00.55.18 port 39774 ssh2
Aug 10 20:22:16 nginx sshd[13820]: pam_unix(sshd:session): session opened for user com by (uid=0)
Aug 10 20:22:16 nginx systemd: pam_unix(systemd-user:session): session opened for user com by (uid=0)
Aug 10 20:22:16 nginx systemd-logind[628]: New session 1493252 of user com.
Aug 10 20:22:16 nginx sshd[13825]: fatal: bad ownership or modes for chroot directory component "/var/www/"
Aug 10 20:22:16 nginx sshd[13820]: pam_unix(sshd:session): session closed for user com
Aug 10 20:22:16 nginx systemd-logind[628]: Removed session 1493252.
Aug 10 20:22:16 nginx systemd: pam_unix(systemd-user:session): session closed for user com
Aug 10 20:22:22 nginx sshd[13832]: reverse mapping checking getaddrinfo for 79-0055-18.dyn.broadband.iskratelecom.ru [79.00.55.18] failed - POSSIBLE BREAK-IN ATTEMPT!
Aug 10 20:22:22 nginx sshd[13832]: Accepted password for com from 79.00.55.18 port 39775 ssh2
Aug 10 20:22:22 nginx sshd[13832]: pam_unix(sshd:session): session opened for user com by (uid=0)
Aug 10 20:22:22 nginx systemd-logind[628]: New session 1493253 of user com.
Aug 10 20:22:22 nginx systemd: pam_unix(systemd-user:session): session opened for user com by (uid=0)
Aug 10 20:22:22 nginx sshd[13837]: fatal: bad ownership or modes for chroot directory component "/var/www/"
Aug 10 20:22:22 nginx sshd[13832]: pam_unix(sshd:session): session closed for user com
Aug 10 20:22:22 nginx systemd-logind[628]: Removed session 1493253.
Aug 10 20:22:22 nginx systemd: pam_unix(systemd-user:session): session closed for user com
---------- Добавлено 10.08.2017 в 20:25 ----------
права на папку /var/www/com
пробовал
root root
com root
www-data www-data
не помогает
Да, лично уменя блокировка гигантов подняла доход примерно на 10-15%
Если убрать строку
то ssh появляется у рута но нет у com
Всех гигантов пылесосов трафика с копеечными ценами давно занес в бан - гугл, яндекс, букинг, фейсбук - долго перечилять. Они всегда платят мизер
Сори, не заметил
# 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
HostKey /etc/ssh/ssh_host_ed25519_key
#Privilege Separation is turned on for security
UsePrivilegeSeparation yes
# Lifetime and size of ephemeral version 1 server key
KeyRegenerationInterval 3600
ServerKeyBits 1024
# Logging
SyslogFacility AUTH
LogLevel INFO
# Authentication:
LoginGraceTime 120
PermitRootLogin yes
StrictModes yes
RSAAuthentication yes
PubkeyAuthentication yes
#AuthorizedKeysFile %h/.ssh/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 yes
# 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
# 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 yes
---------- Добавлено 10.08.2017 в 14:28 ----------
ааа так я не втот файл все добавлял :)))
---------- Добавлено 10.08.2017 в 15:27 ----------
Теперь такая беда
прописываю в конец файла sshd_config
Subsystem sftp internal-sftp
Match User com
X11Forwarding no
AllowTcpForwarding no
ForceCommand internal-sftp
ChrootDirectory /var/www/com
перезапускаю сервис и уменя вырубает ssh у всех в том числе и у рута. Слава богу ссесию не закрывает и можно откатить изменения.
Что не так?
Укажи настройки в этом файле /etc/ssh/sshd_config
ну выше ведь добавил
# This is the ssh client system-wide configuration file. See
# ssh_config(5) for more information. This file provides defaults for
# users, and the values can be changed in per-user configuration files
# or on the command line.
# Configuration data is parsed as follows:
# 1. command line options
# 2. user-specific file
# 3. system-wide file
# Any configuration value is only changed the first time it is set.
# Thus, host-specific definitions should be at the beginning of the
# configuration file, and defaults at the end.
# Site-wide defaults for some commonly used options. For a comprehensive
# list of available options, their meanings and defaults, please see the
# ssh_config(5) man page.
Host *
# ForwardAgent no
# ForwardX11 no
# ForwardX11Trusted yes
# RhostsRSAAuthentication no
# RSAAuthentication yes
# PasswordAuthentication yes
# HostbasedAuthentication no
# GSSAPIAuthentication no
# GSSAPIDelegateCredentials no
# GSSAPIKeyExchange no
# GSSAPITrustDNS no
# BatchMode no
# CheckHostIP yes
# AddressFamily any
# ConnectTimeout 0
# StrictHostKeyChecking ask
# IdentityFile ~/.ssh/identity
# IdentityFile ~/.ssh/id_rsa
# IdentityFile ~/.ssh/id_dsa
# Port 22
# Protocol 2,1
# Cipher 3des
# Ciphers aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc
# MACs hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160
# EscapeChar ~
# Tunnel no
# TunnelDevice any:any
# PermitLocalCommand no
# VisualHostKey no
# ProxyCommand ssh -q -W %h:%p gateway.example.com
# RekeyLimit 1G 1h
SendEnv LANG LC_*
HashKnownHosts no
GSSAPIAuthentication yes
GSSAPIDelegateCredentials no
DenyGroups com
Subsystem sftp internal-sftp
Match User com
X11Forwarding no
AllowTcpForwarding no
AllowAgentForwarding no
ermitTunnel no
ForceCommand internal-sftp
ChrootDirectory /var/www/com
И покажи запись пользователя в файле /etc/passwd
com:x:1000:1000::/var/www/com:/bin/sh
# This is the ssh client system-wide configuration file. See
# ssh_config(5) for more information. This file provides defaults for
# users, and the values can be changed in per-user configuration files
# or on the command line.
# Configuration data is parsed as follows:
# 1. command line options
# 2. user-specific file
# 3. system-wide file
# Any configuration value is only changed the first time it is set.
# Thus, host-specific definitions should be at the beginning of the
# configuration file, and defaults at the end.
# Site-wide defaults for some commonly used options. For a comprehensive
# list of available options, their meanings and defaults, please see the
# ssh_config(5) man page.
Host *
# ForwardAgent no
# ForwardX11 no
# ForwardX11Trusted yes
# RhostsRSAAuthentication no
# RSAAuthentication yes
# PasswordAuthentication yes
# HostbasedAuthentication no
# GSSAPIAuthentication no
# GSSAPIDelegateCredentials no
# GSSAPIKeyExchange no
# GSSAPITrustDNS no
# BatchMode no
# CheckHostIP yes
# AddressFamily any
# ConnectTimeout 0
# StrictHostKeyChecking ask
# IdentityFile ~/.ssh/identity
# IdentityFile ~/.ssh/id_rsa
# IdentityFile ~/.ssh/id_dsa
# Port 22
# Protocol 2,1
# Cipher 3des
# Ciphers aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc
# MACs hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160
# EscapeChar ~
# Tunnel no
# TunnelDevice any:any
# PermitLocalCommand no
# VisualHostKey no
# ProxyCommand ssh -q -W %h:%p gateway.example.com
# RekeyLimit 1G 1h
SendEnv LANG LC_*
HashKnownHosts no
GSSAPIAuthentication yes
GSSAPIDelegateCredentials no
Subsystem sftp internal-sftp
Match User com
X11Forwarding no
AllowTcpForwarding no
AllowAgentForwarding no
ermitTunnel no
ForceCommand internal-sftp
ChrootDirectory /var/www/com
---------- Добавлено 10.08.2017 в 13:46 ----------
такое впечатление что файл ssh_config не обрабатывается.
прописал туда
в надежде открубить доступ юзера по ssh (юзер в группу добавил и проверил что он там), перезагрузил ssh - но доступ остался.