Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#20377 - [apache] mpm_itk ignores ChrootDir
Attached to Project:
Arch Linux
Opened by Dave Akers (dazoe) - Thursday, 05 August 2010, 03:16 GMT
Last edited by Jan de Groot (JGC) - Tuesday, 17 August 2010, 12:50 GMT
Opened by Dave Akers (dazoe) - Thursday, 05 August 2010, 03:16 GMT
Last edited by Jan de Groot (JGC) - Tuesday, 17 August 2010, 12:50 GMT
|
DetailsDescription:
Useing httpd.itk (mpm_itk) ChrootDir doesn't work as expected and doesn't give any errors. mpm_itk ignores ChrootDir. I've written a patch to add chroot support to mpm_itk and have attached it. It also adds VHostChrootDir which allows chroot per virtual host. |
This task depends upon
Closed by Jan de Groot (JGC)
Tuesday, 17 August 2010, 12:50 GMT
Reason for closing: Won't implement
Additional comments about closing: Upstream doesn't like to add the patch, so don't we.
Tuesday, 17 August 2010, 12:50 GMT
Reason for closing: Won't implement
Additional comments about closing: Upstream doesn't like to add the patch, so don't we.
Comment by Jan de Groot (JGC) -
Thursday, 05 August 2010, 14:55 GMT
Could you take this up with upstream (the mpm-itk developers)?
Comment by Dave Akers (dazoe) -
Thursday, 05 August 2010, 22:30 GMT
I have been commutation with the developer via the mpm_itk mailing list regarding this. So far he seems reluctant to add the patch. But my point is if ChrootDir is a valid config directive then it should work. If mpm_itk doesn't want to add the functionality then one of the patches should remove the directive.
11-chroot.patch