[ANNOUNCE](slightly OT)mod_chroot

[prev] [thread] [next] [Date index for 2005/05/18]

--nextPart1817592.Or9q9t7BDG
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

mod_chroot issues a chroot syscall at the very end of the PostConfig phase.=
=20
Thus all configuration, logfile opening, etc. is done in the normal root bu=
t=20
the workers run with a different root. That new root can be mounted=20
ro,nodev,noexec. Hence all Perl modules can be loaded before the chroot=20
mod_perl's include path can be outside the new root. This is really alpha. =
I=20
have checked it with a few simple PerlResponseHandlers, ModPerl::Registry a=
nd=20
Perl code inside SSI Dokuments with Apache::IncludeHook.

http://foertsch.name/Perl/mod_chroot/mod_chroot-0.01.tar.gz

Actually, my first try was to write it in Perl but the mod_perl's=20
PerlPostConfigHandler is APR_HOOK_MIDDLE. Is it possible to extend the=20
Perl*Handler directives so that the priority can be specified, say=20
"Perl*Handler Handler APR_HOOK_REALLY_LAST+10"? Or is this not possible in=
=20
principle?

Torsten

--nextPart1817592.Or9q9t7BDG
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBCi6t5wicyCTir8T4RAnNfAJ46OKk9QsjpsihixHTQwAP9q5m99ACghZE9
51dZgh2JMpxpmikG6NKs2hE=
=qeFF
-----END PGP SIGNATURE-----

--nextPart1817592.Or9q9t7BDG--