Python script to monitor a file for changes and then mail the report with the file attached.
Published: 21-12-2012 | Author: Remy van Elst | Text only version of this article
❗ This post is over eight years old. It may no longer be up to date. Opinions may have changed.
This is a script which checks a file's md5 hash, compares it to a previous (or given) hash and mails a report with the option of attaching the file with the email. I wrote it because I use AIDE on some systems, and I let it auto update the database. This script runs via cron before and after the AIDE run, so I have an archive of databases. But it can be used for all kind of files, not just for the AIDE database.
Consider sponsoring me on Github. It means the world to me if you show your appreciation and you'll help pay the server costs.
You can also sponsor me by getting a Digital Ocean VPS. With this referral link you'll get $100 credit for 60 days.
- Python 2.7 or above (tested in python 2.7.3 and python 3.3.0)
Clone this git repo:
git clone https://github.com/RaymiiOrg/hash-check-mail.git
Or download it from Raymii.org:
Usage of the script is fairly simple. I'll explain the command line options below:
--checksum-compareThe MD5SUM you wish to compare the file to. If this option is given, the script will not write the checksum to a temp location for comparison (/tmp). This should be used if the checksum of the file is known and should not change.
--overwrite-checksumWhen this option is set, when the checksum of a file has been changed, the script will write the new checksum to the temp file. This way you get an email when a change occurs, but changes are allowed. My AIDE database is known to change, but I still want to know when it changes.
--attach-fileWhen this option is set, the file which is checked is sent as an attachment with the email. My AIDE database gets mailed every time it changes. This way you can inspect the changed file without logging on to the remote system, or keep it for archival purposes.
--smtpHostname or IP address of the SMTP server. Defaults to
Fromaddress of the email. Defaults to
--mail-on-matchWhen this option is set, it mails when the file matches. By default no email is sent when the file checksum matches. With this switch you can force an email when the file checksum has not been changed.
- Monitor the file
/var/lib/aide/aide.db.gz, mail to
firstname.lastname@example.org, overwrite checksum on change and attach the file:
./check-file.py -e "email@example.com" -a -o /var/lib/aide/aide.db.gz
- Monitor the file
/var/lib/aide/aide.db.gzagainst known checksum and mail to
./check-file.py -e "firstname.lastname@example.org" -a -c "41ce523dd72a67039df2db9b4542411c"
- Monitor file
/etc/passwd, send even if md5sum matches, from
email@example.com smtp server
smtp.kpnmail.com, do not attach it to the email and do not overwrite the checksum file:
./check-file.py -e "firstname.lastname@example.org" -f "email@example.com" -s
"smtp.kpnmail.com" -m /etc/passwd
- Cron job to monitor the AIDE database and mail changes every night at 10 PM:
1 22 * * * /usr/bin/python /root/scripts/check-file.py -e "firstname.lastname@example.org" -a
Sample report email
File checksum report (v 0.1). Date: Sat, 15 Dec 2012 21:18:26 +0000. Hostname: aide.raymii.org. Checksum does NOT match. Old: 54b0a4497e2b1d9b8e9dc704838e9047. New: 38293053ec07539050f3efd9d33b310b. Filename: /usr/share/doc/munin-node/README.Debian. I checksummed the file itself. Overwriting old checksum with new checksum as requested. Written checksum 38293053ec07539050f3efd9d33b310b to file /tmp/usr-share-doc-munin-node-README.Debian.md5
Tags: aide , file , ids , intrusion-detection , md5sum , monitoring , python , software
# Copyright (C) 2012 Remy van Elst # This program is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 3 of the License, or # (at your option) any later version. # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # You should have received a copy of the GNU General Public License # along with this program. If not, see <http://www.gnu.org/licenses/>.