Paul, Also, consider the wisdom of using chroot() at all. http://kerneltrap.org/Linux/Abusing_chroot
peruser gives unparalleled security as it allows the whole process to run as the user. Once in user-mode, the kernel can be relied upon to protect files based on normal file and directory permissions. With peruser, apache processes don't even need to have access to apache configuration files. chroot() is, and has always been a poor man's jail implementation that usually causes more holes than it fixes, just in unknown ways (usually dealing with users being able to link in binary libraries in unpredictable ways). - Neal On 10/11/07, Lord Le <[EMAIL PROTECTED]> wrote: > Hi, > > I have a problem with peruser 0.2x (Apache 2.2) and mod_python working > together. > Everything works fine until I set chroot dir in processor config. > All mod_python files are installed in main apache dir and also in chroot. > > I'm not sure if it's peruser problem, but in the fact: > > 1. Main apache + mod_python without setting chroot dir (only with changing > UID/GID) works fine. > 2. Another apache run directly from chroot works fine with mod_python. > 3. Main apache + mod_python with that same configuration as 1 but with > chrooted processor give an error. > > Below is the error write to error log through the apache from mod_python: > > [Thu Oct 11 17:56:35 2007] [error] make_obcallback: could not import > mod_python.apache.\n > ImportError: No module named mod_python.apache > [Thu Oct 11 17:56:35 2007] [error] make_obcallback: Python path being used > "['/usr/lib/python24.zip', '/usr/lib/python2.4', > '/usr/lib/python2.4/plat-linux2', > '/usr/lib/python2.4/lib-tk', > '/usr/lib/python2.4/lib-dynload', > '/usr/local/lib/python2.4/site-packages', > '/usr/lib/python2.4/site-packages']". > [Thu Oct 11 17:56:35 2007] [error] python_handler: no interpreter callback > found. > > I could see this error every time I open a python script, but also every > time when peruser processor is created (for example to handle standard > non-python request). > > I have absolutely no idea what's wrong. Is here anybody who knows how fix > this? Anybody run mod_python under chrooted processor? > > Thanks for your time. > > Best regards, > Paul > > _______________________________________________ > Peruser mailing list > [email protected] > http://www.telana.com/mailman/listinfo/peruser > > _______________________________________________ Peruser mailing list [email protected] http://www.telana.com/mailman/listinfo/peruser
