From owner-freebsd-questions@freebsd.org Mon Jun 25 17:45:12 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 76B4E10187F3 for ; Mon, 25 Jun 2018 17:45:12 +0000 (UTC) (envelope-from freebsd-en@lists.vlassakakis.de) Received: from dd14614.kasserver.com (dd14614.kasserver.com [85.13.136.14]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 17412868EE for ; Mon, 25 Jun 2018 17:45:11 +0000 (UTC) (envelope-from freebsd-en@lists.vlassakakis.de) Received: from [192.168.3.55] (p50927CA7.dip0.t-ipconnect.de [80.146.124.167]) by dd14614.kasserver.com (Postfix) with ESMTPSA id E120B43C10C9 for ; Mon, 25 Jun 2018 19:45:02 +0200 (CEST) From: Philipp Vlassakakis Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: FreeBSD 11.1: chroot users / provide pre-built binaries Message-Id: Date: Mon, 25 Jun 2018 19:45:02 +0200 To: freebsd-questions@freebsd.org X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Jun 2018 17:45:12 -0000 Hello, everybody, I am currently looking for a good solution to my =E2=80=9Eproblem=E2=80=9C= . Scenario: I have a fileserver with several hundreds local users. Each user should be locked into his $HOME (so they can=E2=80=99t cd into = any other user-directory, /root etc.), but can login via SSH,SFTP and = upload files.=20 Via ZFS exec,devices,setuid is set to =E2=80=9Eoff", so they can't = execute any self-uploaded binaries, except binaries, which are provided = by me. (cp, mv, rm, rmdir, sh, touch, chgrp, groups, pwd etc.). =20 The binaries are included via $PATH. On the one hand I want to save space, so that the binairies don't have = to be in every $HOME,=20 on the other hand the work is reduced if a binary needs to be updated. Is there any simple way to lock users into their Home-Directory without = editing sshd_config every time? Thanks in advance Regards, Philipp=