Apache ITK vs Suexec -
what benefit of using itk module instead of suexec running apache server? idea same, run scripts owner privileges instead of nobody, www or apache!
is better use itk in favor of suexec? if so, why? security , performance in comparison?
mpm-itk allows run apache per-user credentials instead of under apache user/group. suexec runs scripts cgi under specific user/group, static files served apache still need more open permissions accessed.
mpm-itk allows apache modules (mod_php, etc) run under specific user:group static files having same permissions scripts. main downside apache's control process has run root (with reduced privileges) can switch user after request parsed. suexec not have security risk, solution script execution (not website content isolation).
here a blog post summary regarding mpm-itk vs suexec , other solutions. author accepts security implications of mpm-itk opinion out-weighs drawbacks of competing solutions. not agree author apache exploit less succeed because mpm-itk patch in use, recommend staying date on security patches (we should anyway, right?) if willing accept security risk per-user benefit.
in summary, mpm-itk vs suexec per-situation decision. solution beyond mpm-itk per-user apache instances behind reverse proxy, if server resources not concern. read more here: http://wiki.apache.org/httpd/extendingprivilegeseparation
But suexec is setuid binary so it has security risk too...
ReplyDelete