Symlinks & chroot - Is it Possible?
Drew Tomlinson
drew at mykitchentable.net
Sun Apr 4 08:59:03 PDT 2004
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
>
More information about the freebsd-questions
mailing list