Skip to content

Instantly share code, notes, and snippets.

@PhilETaylor

PhilETaylor/gist:19edb19a7b6c0cef6d8cc434ba550cac

Created January 30, 2020 12:56
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save PhilETaylor/19edb19a7b6c0cef6d8cc434ba550cac to your computer and use it in GitHub Desktop.
Save PhilETaylor/19edb19a7b6c0cef6d8cc434ba550cac to your computer and use it in GitHub Desktop.
Download ZIP
Raw
gistfile1.txt
The ONLY time the md5 hash of those files should change is when you change the file.
The only time the files need to be changed is when a site is upgraded. However, even then, if there are no changes in the new version in those files then the hash can remain the same.
We cache the md5 hash of the file into a file, in the same folder, buy proceeded with a period (.)
On every page load of the website we compare the md5 hash of the monitored files, with the cached md5 hash in the lock file we created.
If they are different then SOMETHING has changed in the monitored file, and we alert you on that.
The current md5 hashes for Joomla 3.9.15 are available through our free service here
https://corefiles.myjoomla.io/stat/joomla/3.9.15/includes/framework.php = 9755179f38c093ab892414e89f5d4433
https://corefiles.myjoomla.io/stat/joomla/3.9.15/includes/defines.php = b155a49cb182672bf515347c0c7843bf
I have completed an audit of http://www.contentiteit.nl and the tools show there are no modified core files on this site at the moment.
Kindest regards
Phil.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment