Difference between revisions of "SFTP chroot"

From ArchWiki
Jump to: navigation, search
m (Add to new category.)
(Fix typo's, better write bind example, added configuration on Installing)
 
(78 intermediate revisions by 25 users not shown)
Line 1: Line 1:
 
[[Category:File Transfer Protocol]]
 
[[Category:File Transfer Protocol]]
[[Category:Security]]
+
[[Category:Secure Shell]]
OpenSSH 4.9+ includes a built-in chroot for sftp, but requires a few tweaks to the normal install.
+
[[ja:SFTP chroot]]
 +
{{Related articles start}}
 +
{{Related|SSHFS}}
 +
{{Related articles end}}
  
==Installation==
+
[[OpenSSH]] 4.9+ includes a built-in chroot for sftp, but requires a few tweaks to the normal install.
This package is available in the core repository. To install it, run
+
 
# pacman -S openssh
+
== Installation ==
 +
 
 +
[[Install]] and configure [[OpenSSH]]. Once running, make sure {{ic|sftp-server}} has been set correctly:
 +
 
 +
{{hc|/etc/ssh/sshd_config|
 +
Subsystem sftp /usr/lib/ssh/sftp-server
 +
}}
 +
 
 +
Access files with ''sftp'' or [[SSHFS]]. Many standard [[List_of_applications#File_transfer_clients|FTP clients]] should work as well.
  
 
==Configuration==
 
==Configuration==
In /etc/ssh/sshd_config, modify the Subsystem line for sftp:
 
  Subsystem      sftp    internal-sftp
 
  
At the end of the file, add something similar to the following for a group:
+
===Setup the filesystem===
  Match Group sftpusers
+
 
    ChrootDirectory %h
+
Bind mount the live [[filesystem]] to be shared to this directory. In this example, {{ic|/mnt/data/share}} is to be used, owned by [[user]] {{ic|root}} and has octal [[permissions]] of {{ic|755}}:
    ForceCommand internal-sftp
+
 
    AllowTcpForwarding no
+
# chown root:root /mnt/data/share
 +
# chmod 755 /mnt/data/share
 +
# mkdir -p /srv/ssh/jail
 +
# mount -o bind /mnt/data/share /srv/ssh/jail
 +
 
 +
Add entries to [[fstab]] to make the bind mount survive on a reboot:
 +
/mnt/data/share /srv/ssh/jail  none  bind  0  0
 +
 
 +
{{Note|Readers may select a file access scheme on their own.  For example, optionally create a subdirectory for an incoming (writable) space and/or a read-only space.  This need not be done directly under {{ic
 +
|/srv/ssh/jail}} - it can be accomplished on the live partition which will be mounted via a bind mount as well.
 +
}}
 +
 
 +
=== Create an unprivileged user ===
 +
{{Note|You do not need to create a group, it is possible to use {{ic|Match User}} instead of {{ic|Match Group}}.}}
 +
 
 +
Create the {{ic|sftponly}} [[group]]:
 +
 
 +
# groupadd sftponly
 +
 
 +
Create a [[user]] that uses `sftponly` as main group:
 +
 
 +
# useradd -g sftponly -d ''/srv/ssh/jail'' ''username''
 +
 
 +
Set a (complex) password - to prevent {{ic|account is locked}} error:
 +
 
 +
# passwd ''username''
 +
 
 +
You many to deny [[shell]] login access for the user:
 +
 
 +
# usermod -s /sbin/nologin ''username''
 +
 
 +
=== Configure OpenSSH ===
 +
{{Note|You may want to use {{ic|Match User}} instead of {{ic|Match Group}} as been given in the previous step.}}
 +
 
 +
{{hc|/etc/ssh/sshd_config|<nowiki>
 +
Subsystem sftp /usr/lib/ssh/sftp-server
 +
 
 +
Match Group sftponly
 +
  ChrootDirectory %h
 +
  ForceCommand internal-sftp
 +
  AllowTcpForwarding no
 +
  X11Forwarding no
 +
  PasswordAuthentication no
 +
</nowiki>}}
  
Or for a user:
+
[[Restart]] {{ic|sshd.service}} to confirm the changes.
  Match User username
 
    ChrootDirectory %h
 
    ForceCommand internal-sftp
 
  
The %h represents the users home directory.
+
==== Fixing path for authorized_keys ====
 +
{{Tip|Use the [[SSH_keys#Key_ignored_by_the_server|debug mode]] of OpenSSH on the client and server in case of {{ic|(pre)auth}} error(s).}}
 +
With the standard path of ''AuthorizedKeysFile'', the [[SSH keys]] authentication will fail for chrooted-users. To fix this, [[append]] a root-owned directory on ''AuthorizedKeysFile'' to {{ic|/etc/openssh/sshd_config}} e.g. {{ic|/etc/ssh/authorized_keys}}, as example:
  
Change ownership of chrooted dir to root (for more details see at the end):
+
{{hc|/etc/ssh/sshd_config|
chown root ~user
+
AuthorizedKeysFile ''/etc/ssh/authorized_keys/%u'' .ssh/authorized_keys
 +
PermitRootLogin no
 +
PasswordAuthentication no
 +
PermitEmptyPasswords no
 +
Subsystem sftp /usr/lib/ssh/sftp-server
 +
}}
  
Restart sshd:
+
Create ''authorized_keys'' folder, generate a [[SSH_keys#Choosing_the_key_location_and_passphrase|SSH-key]] on the client, [[SSH_keys#Manual_method|copy]] the contents of the key to {{ic|/etc/ssh/authorized_keys}} (or any other preferred method) of the server and [[SSH_keys#Key_ignored_by_the_server|set correct permissions]]:
# /etc/rc.d/sshd restart
 
  
===Adding new chrooted users===
+
# mkdir /etc/ssh/authorized_keys
If using the group method above, ensure all sftp users are put in the appropriate group, i.e.:
+
# chown root:root /etc/ssh/authorized_keys
  usermod -g sftpusers
+
# chmod 755 /etc/ssh/authorized_keys
 +
# echo 'ssh-rsa <key> <username@host>' >> ''/etc/ssh/authorized_keys/username''
 +
# chmod 644 /etc/ssh/authorized_keys/''username''
  
Also, set their shell to /bin/false to prevent a normal ssh login:
+
[[Restart]] {{ic|sshd.service}}.
  usermod -s /bin/false
 
  
Note that since this is only for sftp, a proper chroot environment with a shell and /dev/* doesn't need to be created.
+
==Tips and tricks==
 +
=== Write permissions ===
 +
The [[#Setup the filesystem|bind]] path needs to be fully owned by {{ic|root}}, however files and/or subdirectories don't have to be.
 +
In the following example the [[user]] ''www-demo'' uses {{ic|/srv/ssh/www/demo}} as the jail-directory:
 +
# mkdir /srv/ssh/www/demo/public_html
 +
# chown www-demo:sftponly /srv/ssh/www/demo/public_html
 +
# chmod 775 /srv/ssh/www/demo/public_html
  
Their chroot will be the same as their home directory. The permissions are not the same as a normal home, though. Their home directory must be owned as root and not writable by another user or group. This includes the path leading to the directory. My recommendation is to use /usr/local/chroot as a root and build the home directories under that.
+
The user should now be able to create files/subdirectories inside this directory. See [[File permissions and attributes]] for more information.
  
==Logging==
+
=== Logging ===
 +
{{Accuracy|Is this possible with systemd-journal? Are there no security concerns?}}
  
'''1)'''
+
The user will not be able to access {{ic|/dev/log}}. This can be seen by running {{ic|strace}} on the process once the user connects and attempts to download a file.
  
The user will not be able to access {{ic|/dev/log}}. This can be seen by running {{ic|strace}} on the process once the user connects and attempts to download a file. Create the sub-dircetory {{ic|dev}} in the {{ic|ChrootDirectory}}, for example:
+
==== Create sub directory ====
  sudo mkdir /usr/local/chroot/theuser/dev
+
Create the sub-directory {{ic|dev}} in the {{ic|ChrootDirectory}}, for example:
  sudo chmod 755 /usr/local/chroot/theuser/dev
+
# mkdir /usr/local/chroot/user/dev
 +
# chmod 755 /usr/local/chroot/user/dev
  
 
{{ic|syslog-ng}} will create the device {{ic|/usr/local/chroot/theuser/dev/log}} once configured.
 
{{ic|syslog-ng}} will create the device {{ic|/usr/local/chroot/theuser/dev/log}} once configured.
  
'''2)'''
+
==== Syslog-ng configuration ====
 
 
 
Add to {{ic|/etc/syslog-ng/syslog-ng.conf}} a new source for the log and add the configuration, for example change the section:
 
Add to {{ic|/etc/syslog-ng/syslog-ng.conf}} a new source for the log and add the configuration, for example change the section:
 
{{bc|<nowiki>source src {
 
{{bc|<nowiki>source src {
Line 77: Line 140:
 
}}
 
}}
  
(Optional) If you'd like to similarly log SSH messages to it's own file:
+
(Optional) If you would like to similarly log SSH messages to its own file:
  
 
{{bc|<nowiki>#sshd configuration
 
{{bc|<nowiki>#sshd configuration
Line 84: Line 147:
 
log { source(src); filter(f_ssh); destination(ssh); };</nowiki>
 
log { source(src); filter(f_ssh); destination(ssh); };</nowiki>
 
}}
 
}}
(From [[Syslog-ng#Move_log_to_another_file]])
+
(From [[Syslog-ng#Move log to another file]])
  
'''3)'''
+
==== OpenSSH configuration ====
  
 
Edit {{ic|/etc/ssh/sshd_config}} to replace all instances of {{ic|internal-sftp}} with {{ic|internal-sftp -f AUTH -l VERBOSE}}
 
Edit {{ic|/etc/ssh/sshd_config}} to replace all instances of {{ic|internal-sftp}} with {{ic|internal-sftp -f AUTH -l VERBOSE}}
  
'''4)'''
+
==== Restart service ====
  
Restart logging and SSH:
+
[[Restart]] service {{ic|syslog-ng}} and {{ic|sshd}}.
  /etc/rc.d/syslog-ng restart
 
  /etc/rc.d/ssh restart
 
  
 
{{ic|/usr/local/chroot/theuser/dev/log}} should now exist.
 
{{ic|/usr/local/chroot/theuser/dev/log}} should now exist.
  
==Testing your chroot==
+
== Alternatives to SFTP ==
# ssh username@localhost
+
 
 +
=== Secure copy protocol (SCP) ===
 +
Installing {{Pkg|openssh}} provides the ''scp'' command to transfer files. SCP may be faster than using SFTP [https://superuser.com/questions/134901/whats-the-difference-between-scp-and-sftp].
 +
 
 +
[[Install]] {{Aur|rssh}} or {{Pkg|scponly}} as alternative shell solutions.
 +
 
 +
==== Scponly ====
 +
 
 +
[[install]] {{Pkg|scponly}}.
  
should refuse the connection or fail on login. The response varies, possibly due to the version of OpenSSH used.
+
For existing users, simply set the user's shell to scponly:
  
  # sftp username@localhost
+
  # usermod -s /usr/bin/scponly ''username''
  
should place you in the chroot'd environment.
+
See [https://github.com/scponly/scponly/wiki the Scponly Wiki] for more details.
  
==Troubleshooting==
+
==== Adding a chroot jail ====
Error while trying to connect
 
Write failed: Broken pipe                                                                                             
 
Couldn't read packet: Connection reset by peer
 
If you also find similar message in /var/log/auth.log
 
sshd[12399]: fatal: bad ownership or modes for chroot directory component "/path/of/chroot/directory/" 
 
  
It's ChrootDirectory ownership problem, sshd will reject sftp connections to accounts that are set to chroot into any directory that has ownership/permissions that sshd doesn't consider secure. sshd's apparently strict ownership/permissions requirements dictate that every directory in the chroot path must be owned by root and only writable for the owner. So, for example, if the chroot environment is in a user's home directory both /home and /home/username must be owned by root and have permissions along the lines of 755 or 750 ( group ownership should allow user to access ).
+
The package comes with a script to create a chroot. To use it, run:
  
If chroot environment is in user's home directory, make sure user have access to it's home directory, or user would not be able to access it's publickey, produce following error
+
# /usr/share/doc/scponly/setup_chroot.sh
Permission denied (publickey).
+
* Provide answers
 +
* Check that {{ic|/path/to/chroot}} has {{ic|root:root}} owner and {{ic|r-x}} for others
 +
* Change the shell for selected user to {{ic|/usr/bin/scponlyc}}
 +
* sftp-server may require some libnss modules such as libnss_files. Copy them to chroot's {{ic|/lib}} path.
  
==Links & References==
+
== See also ==
 
*[http://www.minstrel.org.uk/papers/sftp/ http://www.minstrel.org.uk/papers/sftp/builtin/]
 
*[http://www.minstrel.org.uk/papers/sftp/ http://www.minstrel.org.uk/papers/sftp/builtin/]
 
*[http://www.openbsd.org/cgi-bin/man.cgi?query=sshd_config http://www.openbsd.org/cgi-bin/man.cgi?query=sshd_config]
 
*[http://www.openbsd.org/cgi-bin/man.cgi?query=sshd_config http://www.openbsd.org/cgi-bin/man.cgi?query=sshd_config]

Latest revision as of 15:38, 16 August 2017

OpenSSH 4.9+ includes a built-in chroot for sftp, but requires a few tweaks to the normal install.

Installation

Install and configure OpenSSH. Once running, make sure sftp-server has been set correctly:

/etc/ssh/sshd_config
Subsystem sftp /usr/lib/ssh/sftp-server

Access files with sftp or SSHFS. Many standard FTP clients should work as well.

Configuration

Setup the filesystem

Bind mount the live filesystem to be shared to this directory. In this example, /mnt/data/share is to be used, owned by user root and has octal permissions of 755:

# chown root:root /mnt/data/share
# chmod 755 /mnt/data/share
# mkdir -p /srv/ssh/jail
# mount -o bind /mnt/data/share /srv/ssh/jail

Add entries to fstab to make the bind mount survive on a reboot:

/mnt/data/share /srv/ssh/jail  none   bind   0   0
Note: Readers may select a file access scheme on their own. For example, optionally create a subdirectory for an incoming (writable) space and/or a read-only space. This need not be done directly under /srv/ssh/jail - it can be accomplished on the live partition which will be mounted via a bind mount as well.

Create an unprivileged user

Note: You do not need to create a group, it is possible to use Match User instead of Match Group.

Create the sftponly group:

# groupadd sftponly 

Create a user that uses `sftponly` as main group:

# useradd -g sftponly -d /srv/ssh/jail username

Set a (complex) password - to prevent account is locked error:

# passwd username

You many to deny shell login access for the user:

# usermod -s /sbin/nologin username

Configure OpenSSH

Note: You may want to use Match User instead of Match Group as been given in the previous step.
/etc/ssh/sshd_config
Subsystem sftp /usr/lib/ssh/sftp-server

Match Group sftponly
  ChrootDirectory %h
  ForceCommand internal-sftp
  AllowTcpForwarding no
  X11Forwarding no
  PasswordAuthentication no

Restart sshd.service to confirm the changes.

Fixing path for authorized_keys

Tip: Use the debug mode of OpenSSH on the client and server in case of (pre)auth error(s).

With the standard path of AuthorizedKeysFile, the SSH keys authentication will fail for chrooted-users. To fix this, append a root-owned directory on AuthorizedKeysFile to /etc/openssh/sshd_config e.g. /etc/ssh/authorized_keys, as example:

/etc/ssh/sshd_config
AuthorizedKeysFile /etc/ssh/authorized_keys/%u .ssh/authorized_keys
PermitRootLogin no
PasswordAuthentication no
PermitEmptyPasswords no
Subsystem sftp /usr/lib/ssh/sftp-server

Create authorized_keys folder, generate a SSH-key on the client, copy the contents of the key to /etc/ssh/authorized_keys (or any other preferred method) of the server and set correct permissions:

# mkdir /etc/ssh/authorized_keys
# chown root:root /etc/ssh/authorized_keys
# chmod 755 /etc/ssh/authorized_keys
# echo 'ssh-rsa <key> <username@host>' >> /etc/ssh/authorized_keys/username
# chmod 644 /etc/ssh/authorized_keys/username

Restart sshd.service.

Tips and tricks

Write permissions

The bind path needs to be fully owned by root, however files and/or subdirectories don't have to be. In the following example the user www-demo uses /srv/ssh/www/demo as the jail-directory:

# mkdir /srv/ssh/www/demo/public_html
# chown www-demo:sftponly /srv/ssh/www/demo/public_html
# chmod 775 /srv/ssh/www/demo/public_html

The user should now be able to create files/subdirectories inside this directory. See File permissions and attributes for more information.

Logging

Tango-inaccurate.pngThe factual accuracy of this article or section is disputed.Tango-inaccurate.png

Reason: Is this possible with systemd-journal? Are there no security concerns? (Discuss in Talk:SFTP chroot#)

The user will not be able to access /dev/log. This can be seen by running strace on the process once the user connects and attempts to download a file.

Create sub directory

Create the sub-directory dev in the ChrootDirectory, for example:

# mkdir /usr/local/chroot/user/dev
# chmod 755 /usr/local/chroot/user/dev

syslog-ng will create the device /usr/local/chroot/theuser/dev/log once configured.

Syslog-ng configuration

Add to /etc/syslog-ng/syslog-ng.conf a new source for the log and add the configuration, for example change the section:

source src {
  unix-dgram("/dev/log");
  internal();
  file("/proc/kmsg");
};

to:

source src {
  unix-dgram("/dev/log");
  internal();
  file("/proc/kmsg");
  unix-dgram("/usr/local/chroot/theuser/dev/log");
};

and append:

#sftp configuration
destination sftp { file("/var/log/sftp.log"); };
filter f_sftp { program("internal-sftp"); };
log { source(src); filter(f_sftp); destination(sftp); };

(Optional) If you would like to similarly log SSH messages to its own file:

#sshd configuration
destination ssh { file("/var/log/ssh.log"); };
filter f_ssh { program("sshd"); };
log { source(src); filter(f_ssh); destination(ssh); };

(From Syslog-ng#Move log to another file)

OpenSSH configuration

Edit /etc/ssh/sshd_config to replace all instances of internal-sftp with internal-sftp -f AUTH -l VERBOSE

Restart service

Restart service syslog-ng and sshd.

/usr/local/chroot/theuser/dev/log should now exist.

Alternatives to SFTP

Secure copy protocol (SCP)

Installing openssh provides the scp command to transfer files. SCP may be faster than using SFTP [1].

Install rsshAUR or scponly as alternative shell solutions.

Scponly

install scponly.

For existing users, simply set the user's shell to scponly:

# usermod -s /usr/bin/scponly username

See the Scponly Wiki for more details.

Adding a chroot jail

The package comes with a script to create a chroot. To use it, run:

# /usr/share/doc/scponly/setup_chroot.sh
  • Provide answers
  • Check that /path/to/chroot has root:root owner and r-x for others
  • Change the shell for selected user to /usr/bin/scponlyc
  • sftp-server may require some libnss modules such as libnss_files. Copy them to chroot's /lib path.

See also