I want to migrate from mod_fastcgi to mod_fcgid, and I just realized, mod_fcgid supports FcgidWrapper in .htaccess files. Which is nice for dedicated servers. However, I want to provide the web service with mod_fcgid in a shared hosting environment. Customers using .htaccess are able to reconfigure the default PHP settings (by specifying other config file) which could lead to server compromise. I hope you understand the importance of this matter.
A compile-time define for mod_fcgid may be the only practical way to implement this; I don't think the httpd configuration mechanism provides a way to address this issue.
That would be fine as well, currently I am using a dirty patch for disabling the htaccess support.
First, individual directives may be manipulated in httpd 2.3-beta. Secondly, mod_fcgid directives *should* be subject to the 'Files' overrides restriction just as handlers/cgi are. Reclassing as a bug.
Created attachment 30868 [details] Patch - add new directive: FcgidHtaccessCommands
We're moving our large shared hosting to mod_fcgid as well and ran into this issue. It important for us to be able to restrict our users from executing arbitrary commands from the http server's process.
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd. As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd. If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question. If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with. Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.