Date: Sun, 04 Apr 2004 08:59:03 -0700 From: Drew Tomlinson <drew@mykitchentable.net> To: den <moreau@myrealbox.com> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Symlinks & chroot - Is it Possible? Message-ID: <407030C7.4080307@mykitchentable.net> In-Reply-To: <406F0E9E.8000507@myrealbox.com> References: <406EF598.5000508@mykitchentable.net> <406F0E9E.8000507@myrealbox.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/3/2004 11:21 AM den wrote: > I use mount_null and have no problem with it. You need create dir in > each user home and use mount_null for mount your chrooted dir > with created directories as mount points . > So you need add many lines in your /etc/fstab file . I understand. Thanks for your reply. > I think that words in manual about beta concern writing in directory > that uses mount_null. I don't use write and it seems that you don't > need write too. So use this fs type ( set in fstab "ro" option for > this mount point). > And read man for mount_null. This seems reasonable. Can anyone else comment on their experience using mount_null read only? Thanks, Drew > > Drew Tomlinson wrote: > >> I have a few users that I wish to allow FTP access on my >> 4.9-RELEASE-p4 system. I've setup their accounts and added them to >> /etc/ftpchroot to lock them into their login directories. They are >> in the standard /home/user dirs. >> >> However, I want all of them to have access to another directory >> (/ftp/share) that is setup read-only. I tried adding a symlink to >> /ftp/share but I've found this doesn't work when the user is >> chrooted. I've Googled on this issue. A FAQ for PureFTPd confirms >> this and suggests mount_null. But the man page for mount_null says >> that the code is beta and may wipe out a file system. >> >> What is the best way to achieve my objective? If mount_null is it, >> how do I use it? Do I include it in some sort of login script? I've >> set these users shells to nologin. How would that work? >> >> Thanks, >> >> Drew >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?407030C7.4080307>