Apache 2.2.10

Just in case my blog is a primary source for anyone, Apache HTTPD 2.2.10 is now an official release.  This is primarily a bugfix release, with a number of fixes to proxy esoterica among other things.

One change that isn’t a bugfix is that Apache now supports running chroot as a core feature.  This means the third-party mod_chroot is likely to be obsolete for most users, with possible exceptions amongst those who already use it and rely on its exact behaviour.

About these ads

Posted on October 16, 2008, in apache. Bookmark the permalink. 5 Comments.

  1. I’m unable get apache-2.2.10 started with mod_chroot-0.5. Can you point me in the direction of where it mentions that apache supports running chroot as a core feature? Any documentation on how to do this? I wonder if mod_chroot is in fact incompatible with Apache now??

    The error I continually get when trying to start apache is the following:

    [Sat Jan 10 09:37:30 2009] [notice] mod_chroot: changed root to /var/chroot/apache.
    [Sat Jan 10 09:37:30 2009] [alert] (2)No such file or directory: Can’t chdir to /var/chroot/apache
    [Sat Jan 10 09:37:30 2009] [alert] (2)No such file or directory: Can’t chdir to /var/chroot/apache
    [Sat Jan 10 09:37:30 2009] [alert] (2)No such file or directory: Can’t chdir to /var/chroot/apache
    [Sat Jan 10 09:37:30 2009] [alert] (2)No such file or directory: Can’t chdir to /var/chroot/apache
    [Sat Jan 10 09:37:30 2009] [alert] (2)No such file or directory: Can’t chdir to /var/chroot/apache

    Apache-2.2.9-r1 works fine with mod_chroot.

    Thanks!
    hanji

  2. I got it working. It doesn’t look like mod_chroot is compatible with apache-2.2.10, since they both use the ChrootDir variable. I think it was double chrooting on start. Removing -D chroot and setting the core variable fixed the problem, and apache now starts and is chrooted.

    http://httpd.apache.org/docs/2.2/mod/mpm_common.html

    http://www.uno-code.com/?q=node/157

    hanji

  3. Hmmm. Well, I’m not about to dig into how/whether this affects mod_chroot. Not now, at least.

    As for how to use the feature, the easy way would be to let your browser search for “chroot” in the apache documentation.

  4. I should add: in trunk (Apache 2.3/2.4), the chroot functionality has moved to mod_unixd, along with other unix-family directives User and Group.

  5. Heh. I picked up your first comment via RSS feed and replied. The second one got marked as potential spam (probably because of the URLs) and emailed to me to moderate, so I only just saw it. Glad you fixed it!

Follow

Get every new post delivered to your Inbox.

Join 39 other followers

%d bloggers like this: