On 9/7/05, Adam <[EMAIL PROTECTED]> wrote: > And "web hosting" is not "shell hosting" is it? What does "work with" > mean anyways? You need all the binaries to "work with", and they > need all their libs to function. Sure, you could copy all the binaries > and libraries of the entire OS into the chroot, but then what is the > point of chrooting them at all? What do you think this will protect > you from? >
Work with means using various programs like vim or emacs or sed, etc to manipulate the files. And yes you need the binaries and their associated libraries for each program you want a jailed user to be able to run. You don't need an entire OS made available to you in order to have some sort of useful experience with a shell account. For many people a shell account is just that... access to bash, or zsh, etc. and basic system utils. Maybe lynx... maybe mutt. What it does is allow you to give users access to a shell where they can experiment with their own files but not the files of the machine running the shells. This is the point of chrooting any running program. In the case of a shell it's just the shell binary running in the chroot as opposed to httpd or mysqld, etc. It's a useful idea in some scenarios, in others it's not. Mike
