1.7.1 - Feature and Bugfix Release

Version 1.7.1

Release: April 20, 2018

• New: Tripwire detection mode
• Fixed: Corrected permission issue on log file. (fixes #15)
• Updated: Changed the save path for the Tripwire whitelist file

Version 1.7.0

Release: March 22, 2018

• Feature: Lock files are used to ensure multiple runs of malscan don't stack.
• Feature: Configuration options can now be viewed using the malscan -c command. (fixes #10)
• Feature: Configuration options can now be set using the malscan -s OPTION value command.
• Fixed: malscan will now correctly check for sudo.
• Fixed: malscan will now check to see if the user is in the malscan group, in lieu of being run as sudo.
• Fixed: Notifications are now sent in a more spam-checker-friendly format, reducing issues with notifications ending up in the spam folder.
• Updated: malscan will now use its own freshclam.conf file and /var/lib/malscan signatures directory, to prevent conflicts with ClamAV.
• Updated: The malscan file structure has been updated to conform with the FHS. (fixes #7)
• Updated: Rewrote the install.sh script to support Fedora, Debian, and CentOS/RHEL 7.
• Updated: Created RPM packaging for CentOS/RHEL 6, 7, and Fedora 26/27. (fixes #8)
• Updated: New exhaustive build testing CI pipeline for automated malscan testing.
• Removed: Removed whitelisting and tripwire scanning until it can be re-worked in a later release.
• Removed: Removed reporting until it can be re-developed in a later release.
• Removed: Removed Ubuntu/Debian support while working on packaging.