January 15, By admin Hepsia Control Panel. Introduced to our web hosting platform more than a year ago, the Jail Host functionality has brought a new dimension to the concept of site security. Now the Jail Host option is enabled by default for all newly created hosts to double protect them from intruders. Even though security solutions are getting more and more reliable, hackers seem to always be one step ahead of the game. The truth is that no universal painkiller for hack attacks has been invented yet. If an intruder does manage to break into a website, if Jail Host is enabled, they will not be able to move to another host and spread their malicious activity. This prevents intruders from using the host as a doorway to the rest of the system in the event of an attack. The tight encapsulation works at the Operating System level, which guarantees its efficiency in all possible hacking scenarios.
What will happen to already added hosts?
Donate to FreeBSD. Forums New posts Search forums. What's new New posts Latest activity. Log in Register. Search titles only. Search Advanced search….
Administrators rarely get to have the final say in what technologies their web servers must support. Running Apache in a jail or chroot environment will help limit your server's exposure to vulnerabilities in the web applications. There have been vulnerabilities in Apache's httpd itself, too, and this will help protect you if you fall prey to an exploited vulnerability. It takes work. So, before we launch into configuring Apache in a jail, we have some planning to do. Remember the difference between jail and chroot from Chapter 2.
It only takes a minute to sign up. Connect and share knowledge within a single location that is structured and easy to search. The part that I'm missing is the way privileges are set for the webmasters so that they don't see each others directories. I'm trying to set up a multi-users web server and for that I'd like that each user can use both connect with SSH and SFTP but, most important, only sees their own directory. OVH managed to do that, but after 6 hours searching and trying creating a chroot jail , I don't see how they did it. Maybe it's trivial, but I simply don't see it. In a shared web-hosting environment, there are a couple issues that you need to address right off the bat. Regarding directory permissions and only being able to access your files: what you want to do is set home directory permissions such that the "others" group has no permission whatsoever.