Debian lenny chroot install

If you've copied all required files, but the page still isn't working, you should take a look at the Apache error log.

Usually it tells you where the problem is. These instructions break it in a maddening manner. Note the goofy mix of chroot'd and not-chroot'd directories. The chroot'd DocumentRoot will trigger warnings when apache2 is started; if you ignore those, then everything appears to work OK. However, if the ErrorLog directive uses a chroot'd path, then those warnings somehow trigger a fatal error that causes apache2 to not start at all.

This makes debugging this a real adventure. But, once it's running, the non-chroot'd paths for both ErrorLog and CustomLog seem to work just fine. I'm not sure about the rest. It's possible there's something seriously wrong with my setup, but everything's been working great for months until now , so if there is, I don't know what it is.

I am new to chrooting, so I apologise in advance if I ask silly questions. If he's existing, he will be updated; if not, he will be created. It's not true that "no patches are needed anymore". If your users keep sensible data in their chroot directory, they might be thankful if the administrator does indeed patch OpenSSH once in a while.

Also, it's not true that you cannot break out of a chroot shell. There have been local exploits in the past that made this possible.

I have done the necessary config, but if i have multiple users, how do i chroot each users's home dir? Is there something like this? Good rights are on the files, and same configuration on a similar server 64bits, lenny will work I've surfed a lot and read lot of topics, but nothing more precise on an immedite closed session by the server.

And no error in the logs I am running debian lenny and could not get sftp to work till I changed the subsystem to interal-sftp and not the path to the sftp-server. In some scenarios the chroot patch suits better as the build-in chroot function. Thank you for sharing a very nice web site. Because chrooted directory and all directories above need to be owned by root and writible only by root.

Perhaps, just activating and desactivating the PasswordAuthentication rule in the Match for my user I was extremely frustrated with the same thing.

After a reboot of the whole system it starts to work, just restarting the ssh is not enough. This feature is nice, but it is annoying users can't write to their own main directory. It won't be easy taking them away that right. If anybody helps It will be very pleasure for me. Thanks in advance. Fixed it for me. I finally managed to get this to work on my Ubuntu setup!

I had a problem with it resetting every time I rebooted. Check from mirrorlist a mirror near you that carries armel. You need a recent sid? For this: 1. After install boot with the following command line: qemu-system-arm -M versatilepb -kernel vmlinuz-versatile -hda hda.

For the "--second-stage" part one needs a kernel compiled with options listed in previous section.