SSH jail

[Whitedragon]

Sai siis server ülesse pantud.Nüüd siis sai SSH peale pantud ning tekkis probleem SSH-le jaili panemisega

Kood: Vali kõik

# 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
#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 DEBUG # Leidmaks viga

# Authentication:
LoginGraceTime 120
PermitRootLogin no
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
#################
ChrootDirectory ~
#################
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

Ainuke mida ei suuda paika panna on:
#################
ChrootDirectory ~
#################
debug näitab:
Sep 29 14:50:26 server sshd[3998]: fatal: bad ownership or modes for chroot directory component "/Kaust/"
ls / -la väljund:
drwxrwxrwx 3 root root 4096 Sep 29 12:43 Kaust
ja terminali ei avata.

[antik2]

Ainuke mida ei suuda paika panna on:
#################
ChrootDirectory ~
#################
debug näitab:
Sep 29 14:50:26 server sshd[3998]: fatal: bad ownership or modes for chroot directory component "/Kaust/"
ls / -la väljund:
drwxrwxrwx 3 root root 4096 Sep 29 12:43 Kaust
ja terminali ei avata.

Mis su kasutaja kodukataloog tegelikult on? Vaata /etc/passwd failist järele
Ja minuarust "~" ei saa kasutada sellisel juhul- pigem ChrootDirectory /home/%u

Chroot-i tuleb vaadata nagu ruutkataloogi, sellest ka veateated ligipääsuõigustest.

Edasi teed sama kodukataloogi chroot-i alla nagu on passwd failis kirjas:

# mkdir /home/kasutajanimi/home/kasutajanimi

[illukas]

see kataloog kuhu ta chroodib PEAB olema rootu omanduses ja teistel ei tohi ola kirjutusõigust sinna. Kasutaja kaust võib/peab seal kausta sees olema