A question about chroot

Discussion in 'General' started by rafael-ec, Aug 2, 2007.

  1. rafael-ec

    rafael-ec New Member

    I read in this forums that we can have a chroot environment, by setting one variable to true.
    1)Is there any risk on doing this for all my previous sites? I only have ispconfig on my production server and right now I can't test before doing this kind of things.
    2)Would my previous sites have a chroot enviroment or only de new sites?
    3)The chroot enviroment would be only for the ssh sessions?
    4)Is there a way I can have a separete php.ini for each site? I remeber this could be done with ensim, but could be done with ispconfig?


  2. till

    till Super Moderator Staff Member ISPConfig Developer

    First, to use chrooting, you will have to build a new patched SSH daemon that supports chrooting:


    1) That is not easy to predict, normally there should be no risk as the chroot script just adds a few directories and files to the users directory.
    2) New and updated sites.
    3) Yes.
    4) First you will have to install suphp:


    and then enable SuPHP in ISPConfig. Afterwards you will be able to specify a custom php.ini in the apache directives field with a suphp directive.
  3. rafael-ec

    rafael-ec New Member

  4. till

    till Super Moderator Staff Member ISPConfig Developer

    I'am not aware of any howtos for these topics for centos at the moment.

Share This Page