SimpleSiteAudit
Updates and InstallationUpdatesVERSION 1.5.3 - Additions/changesI have added a new field to the preferences page: "List pf files to rename:" The field consists of a list of comma separated file names to be re-named on discovery. If found, these files will be re-named by giving them a " _renamed.by.ssam" extension. This feature might be useful where you know of certain file names that have caused you problems in the past. Re-naming the file as soon as it is detected, will prevent it being used for malicious purposes. An email alert will be sent on detection. I have added some extra utilities, as follows: VERSION 1.5.2 - Additions/changesPrior to this version, SSAM would not perform a recursive scan on a Windows/IIS server. It would only scan the root, or nominated directory. SSAM is now compatible with Windows/IIS and will perform a full recursive scan.
VERSION 1.5.1 - Additions/changesAdded a file comparison utility, accessible via a new button on the 'Preferences' page (index.php). Courtesy of:
Ross Scrivener http://scrivna.com PHP file diff implementation. Much credit goes to...
Paul's Simple Diff Algorithm v 0.1 (C) Paul Butler 2007 http://www.paulbutler.org
Used and distributed under the zlib/libpng license. InstallationQUICK STARTDownload SSA and unzip the contents. Choose a web site that will act as your 'Master' site Upload all the SSA files to a password-protected directory, directly off the site root, e.g. mastersite.com/ssa Run the file 'index1.php', submit the settings form for each site you wish to monitor and click 'Finished'. This will take you to the preferences form, where, once details are submitted for all your sites, you will be able to run the script and view your logs. RESTRICTIONSWhen scanning a site on a Windows/IIS server via FTP, it is not possible to detect changes in file permissions. Therefore, these changes will not appear in the log. Not so much a restriction, more the nature of the beast. The FTP scan time can vary, depending on, the size of the monitored site, connection speed and conditions between the 'Master' site and the target site. For example, a site with about 5000 files should take about 8 seconds. Larger sites will take longer. It may be necessary, with very large sites, to increase your PHP time-out setting. The time taken should also be considered when setting up Cron jobs. They will need to be spaced out accordingly. FILE AND DIRECTORY NAMESAll file names must remain as is. The SSA directory can be named anything you like. FILE PLACEMENT1. If it doesn't already exist, a 'logs' directory will be created during the set up process. It will be created as an OFFLINE directory, just ABOVE root level, where it is not web-accessible. A file named db_settings.txt will be created in the 'logs' directory, inside a sub-directory with the same name as the web site being monitored, e.g logs/domain.com. This file contains database access details (password is encrypted). FTP access details are stored in the database (password encrypted). 2. Create a directory, just BELOW root level, where you will upload the SimpleSiteAudit files. Name this directory what ever you like, e.g. 'ssa'. This directory should be password protected as it will contain access to sensitive information. RUN THE SETTINGS PAGE (index1.php)1. Upload the files to your new directory and run index1.php in your browser. 2. Complete and submit the FTP and database settings for each site you want to monitor, and then click 'Finished' to move on to the preferences form. Once this is submitted, you are ready to make the first scan. MONITORING SUB-DOMAINS OR SUB-DIRECTORIESTo monitor a sub-domain or sub-directory, the field 'Document root of site being monitored', in the FTP/db set up page, should be entered as, e.g. htdocs/sub-dir-name or the sub-domain-name - a sub-directory can be added to the sub-domain-name if required, e.g. sub-domain-name/sub-dir-name. CREATE AN SSA LOG FILEThe settings form allows the optional creation of a log file, containing all the SimpleSiteAudit script outputs. Details will be saved to the database on the 'Master' server. This table can grow quite large, periodic clearing of the table is recommended, and ability to display and clear the table will be provided after the first changes have been detected. SETTING UP YOUR CRON JOBDuring the SSA set up process a special file, named '_remotewebsitename.tld.php' will be created in the SSA directory for each site being monitored. Your Cron jobs should be aimed at these files, e.g./htdocs/ssa/_remotewebsitename.tld.php - This mechanism saves the need to pass parameters from your Cron job to the script, which is restricted by some ISPs. if you are monitoring more than 1 web site, make sure your Cron jobs are adequately spaced out. DISPLAYING YOUR CRON LOG FILE (Field: 'Path to, and name of your Cron log')This must point to your Cron log file, i.e. the relative path from your SSA installation files. e.g. ../../cronfilename.txt The 'view file' button will not appear if this file does not exist. Recommend leaving this field empty if using the SSA log file and vice versa. The log contents will appear in a read only textarea. Further formatting is not possible due to unknown input by the Cron process itself. There is no 'Clear log' button for this feature. SECONDARY USESThere may be other uses for this software, for example, it could be used to notify someone, or a group of people, that certain files had been uploaded and are now available for download or viewing. I’d be interested to know what other uses it has been put to. Please use the 'Feedback' link. |