iandouglas736
Verified User
- Joined
- Nov 12, 2007
- Messages
- 8
CentOS 5, DA 1.31.1
I have no need (at present) to chroot other services on my small server, or worry about suexec or chrooting' cgi/php but I do have need for multiple people to collaborate on the development of a site and don't want them poking around on the file system, through my other clients' sites, etc..
All I want to to chroot is ssh/ftp, but don't understand the 'best practice' approach in such a way that it doesn't break how DirectAdmin sets things up on my server right now.
I also need to be selective about who I chroot or not -- for example chroot'ing my own login would be pretty counter-productive ;o) but these other guys (using a shared login) need to be locked into their home directory.
Thanks,
ian
I have no need (at present) to chroot other services on my small server, or worry about suexec or chrooting' cgi/php but I do have need for multiple people to collaborate on the development of a site and don't want them poking around on the file system, through my other clients' sites, etc..
All I want to to chroot is ssh/ftp, but don't understand the 'best practice' approach in such a way that it doesn't break how DirectAdmin sets things up on my server right now.
I also need to be selective about who I chroot or not -- for example chroot'ing my own login would be pretty counter-productive ;o) but these other guys (using a shared login) need to be locked into their home directory.
Thanks,
ian