[scponly] scponly + chroot + qmail

[Kaleb Pederson]

That should be fine.  What you probably want to do is set up scponly to chroot 
to some directory below their home directories.  First, you might 
create /home/chroot which contains the chroot environment.  Then, you would 
create all the users home directories within that chroot.  eg.  You would 
create /home/chroot/users/{john,jane,peter...}, each directory being owned by 
the user.  Then, you set the users home directory to 
"/home/chroot//users/{john,jane,peter...}".  Thus, scponly would chroot 
to /home/chroot, and then change directories to /users/<username>.

I use this setup, and it works very well.  I'm sure there are others using 
similar configurations.

Hope I understood what you were asking and that it helps.

--Kaleb

On Friday 30 September 2005 9:08 am, brett wrote:
> qmail-lspawn requires that the user own their home directory, which
> obviously doesn't work with chrooted homedirs.
>
> has anyone out their come up with a clever solution, or have they
> just been patching qmail-lspawn to ignore the directory ownership issue?
>
> thanks,
> brett
>
> _______________________________________________
> scponly mailing list
> scponly at lists.ccs.neu.edu
> https://lists.ccs.neu.edu/bin/listinfo/scponly
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : https://lists.ccs.neu.edu/pipermail/scponly/attachments/20050930/4e5ee8d3/attachment.bin