Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • 4
    Um, maybe identifying the breach(es) and preventing further intrusions would be a more profitable approach? Commented Oct 28, 2014 at 5:49
  • 1
    As long as the user is the owner of the file you cannot prevent modifications of the inode information. Commented Oct 28, 2014 at 6:28
  • Why not just disallow PHP? Seems like a positive idea. Commented Oct 28, 2014 at 13:17
  • I also think that tampering with such low level feature is not the right approach. If I were you I'd research the topic audit. Auditing is targeted to address problems like yours and it does so by collecting information about system changes in a reliable way. Commented Nov 14, 2014 at 11:20