Skip to main content

Security Warning: Enable “Jail Apache” in the “Tweak Settings” ?

Comments

3 comments

  • cPanelMichael
    Hello :) Mod_ruid2 must be compiled in via EasyApache, and then enabled, before this additional security option is available. Thank you.
    0
  • MinaIsaac
    [quote="cPanelMichael, post: 1533741">Hello :) Mod_ruid2 must be compiled in via EasyApache, and then enabled, before this additional security option is available. Thank you.
    Thank you for your reply Michael :) I got two replies from the VPS provider, First message: That would require us to recompile Apache with mod_ruid2 and switch the PHP handler over to DSO. The only issue with this setup is that it uses a vastly different set of file permissions from the current PHP handler on the vps, suPHP. Sites may not resolve properly until their permissions are fixed after making that sort of change. Second message: This is in an experimental state at this time and we would be unable to assist you with it short of compiling it into apache. If you would like us to compile it in we would need to recompile the server again. I became so confused after these 2 messages. I'm providing hosting services to customers under my VPS and don't want to affect any of my customers' websites resolving, permissions, etc.. So, can you give me advice whether to proceed with the compile or not? Thank you. Best Regards.
    0
  • quizknows
    DSO normally needs different permissions than SuPHP for webapps to write to their own files, however, with ruid2 since Apache is jailed it should run with proper permissions for the sites to function. You wont have issues with sites resolving, as this does nothing to DNS. You might run into file permission issues but that is doubtful in my opinion. That being said RUID2 is still experimental and I personally would recommend using CloudLinux instead, until the issues with modsecurity and ruid2 are resolved (at the very least).
    0

Please sign in to leave a comment.