Daniel Rossi wrote:
ive worked around it by setting USER and HOME to $LOGINUSER or
whatever it is in bashrc. Then call cd to move into the right
directory. So ownership of the files should still be ok without the
same user id ? I believe if the files are owned different to that
uid suexec for instance in apache will complain hence why its that
that way. I see in the jk_chroot source that the environment
variables are set there, but instead of the user logging in its the
user of the user id. Are you saying my work around is not doable ?
if it works that it's doable ;-)
I think it's also possible to rewrite some of the jk_chrootsh code
such that such a setup will work with jk_chrootsh without
sacrificing any of the security checks.