Hi, > when you want a much more strict policy? The only way to defend the > virtual hosts from each other to create different content types just > like http_sys_virthost1_t, http_sys_virthost2_t etc and different . > Imagine users want run php scripts. If you just enable to exec all types > of php scripts there's a chance that you will weaken you security. Not > sure but there's a chance. you may still combine this with suexec, php's safedir options, etc. Don't forget that there is no 100 percent security, but just a lot of methods to get close to 100 percent :-) With kind regards, Daniel S. Reichenbach -- blog - http://people.best-off.org/~dsr/ gpg - http://people.best-off.org/~dsr/gpg.asc work - http://www.best-off.org/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.caosity.org/pipermail/centos/attachments/20050311/f611c0d3/attachment.bin