note 35032 added to security.index

Why not chroot the whole Apache Web Server (or any other Web Server running under UNIX)? After that, Apache will run inside chroot jail, limiting by that access to server's filesystem. For me, that's the first step in the process of securing PHP installations. Also, for people running Linux, look at www.grsecurity.net (don't take this as a sort of marketing ;), which is a great kernel security-related patch. ---- Manual Page -- http://www.php.net/manual/en/security.index.php Edit Note -- http://master.php.net/manage/user-notes.php?action=edit+35032 Delete Note -- http://master.php.net/manage/user-notes.php?action=delete+35032&report=yes Reject Note -- http://master.php.net/manage/user-notes.php?action=reject+35032&report=yes