Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
apache22 >= 2.2.10, and we're now on 2.2.21.
Ideally this would instead accept apache22 older than 2.2.10, but
given how old (and insecure) that is there's not much point. I guess
if anyone really really wants to do that they can revert this change
locally... but I can't say I recommend it.
|
|
While here
* Set LICENSE=gnu-gpl-v2
* Marked as CONFLICTS with apache>=2.2.10.
It provides builtin ChrootDir directive, as PR#44458.
2005-01-09 Hobbit
* getenv()/setenv() instead of flaky getppid().
* fixed layout to make <IfModule> work as expected.
* documentation updates.
* released mod_chroot/0.4
2005-06-12 Hobbit
* fixed a problem with some CGIs (mod_cgid, mod_fcgid)
being executed outside the chroot jail.
Patch by <clement.hermann*free.fr>, thanks!
* updated documentation
* released mod_chroot/0.5
|
|
|
|
so PKG_DESTDIR_SUPPORT not turned on
|
|
|
|
Allow apache22 in some more case and add a hack to devel/subversion
to determine the module by the state of the apache22 option.
This comes from www/ap2-subversion and should be fixed to properly
use build options or so.
OK agc@
|
|
|
|
* Use PKG_APACHE_ACCEPTED.
|
|
|
|
of the shlib major bump.
PKGREVISION++ for the dependencies.
|
|
|
|
|
|
|
|
|
|
chroot environment.
mod_chroot makes running Apache in a secure chroot environment easy.
You don't need to create a special directory hierarchy containing
/dev, /lib, /etc...
mod_chroot allows you to run Apache in a chroot jail with no additional files.
The chroot() system call is performed at the end of startup procedure - when
all libraries are loaded and log files open.
|