Skip to main content

Why does Security Advisor report "Apache vhosts are not segmented or chroot()ed"?

Bill Bailey
  • Updated

Question

Why does Security Advisor report "Apache vhosts are not segmented or chroot()ed"?

 

Answer

You will see this notice when your server is not configured to load user sites in a jailed environment. When a server is configured without jailed users, users may have access to data outside of their environment. The notice can be removed by following the procedure below.

 

Procedure

  1. Check to see if mod_ruid2 is installed on your server. This can be done from the command line or WHM.

    From the command line, run the following command.

    rpm -qa|grep mod_ruid2
    From WHM:
    1. Navigate to "Home » Software » EasyApache 4."
    2. Click the "View all Packaged" button in the "Currently Installed Packages" box.
    3. Look for "mod_ruid" in the "Apache 2.4" section.
  2. If mod_ruid2 is not installed, it can be installed from "EasyApache 4" in WHM.
    1. Navigate to "Home » Software » EasyApache 4."
    2. Click the "Customize" button in the "Currently Installed Packages" box.
    3. Click "Apache Modules."
    4. Enter "mod_ruid2" in the "Search" box.
    5. Click the toggle to the right of "mod_ruid2."
    6. Click "Review."
    7. Click the "Provision" button.
  3. Navigate to "Home » Server Configuration » Tweak Settings" in WHM.
  4. Click on the "Security" tab.
  5. Scroll down to "EXPERIMENTAL: Jail Apache Virtual Hosts using mod_ruid2 and cPanel® jailshell."
  6. Select the "On" option next to "EXPERIMENTAL: Jail Apache Virtual Hosts using mod_ruid2 and cPanel® jailshell."
  7. Click the "Save" button.
  8. Navigate to "Home » Account Functions » Manage Shell Access" in WHM.
  9. Deselect the "Jailed" and "Disabled" checkboxes.
  10. Click the "Apply to" button under "Jailed Shell" to change the shell of accounts from Normal to Jailed.
  11. Click the "OK" button in the "Are you sure?" pop-up.

Related articles