Mute Screamer 1.0.6 has been released. This updated fixes a minor bug with the update hashes. They seem to be out of date on the PHPIDS website, so I’ve rolled my own solution for now.
This should fix the problem some users were having problems with the updater asking users to update when the files were the same.
Mute Screamer 1.0.4 is out. This release brings some minor improvements and WordPress 3.3 compatibility and also some minor bug fixes. For full details checkout the changelog.
Mute Screamer 1.0.3 is now available in the WordPress plugin directory. This is a minor update which addresses some bug fixes and improves compatibility with WordPress 3.2.
See the changelog for full details.
Mute Screamer 1.0.1 is a maintenance release which fixes numerous bugs.
This release fixes the automatic updates from PHPIDS.
PHPIDS recently updated their project tracking software, so a few changes were needed to get the updates from PHPIDS working again.
See the changelog for full details.
Following the latest release of WordPress comes the latest version of Mute Screamer.
Get your copy or update via the WordPress admin.
The biggest change in this release is ip banning and attack throttling.
You can configure Mute Screamer to ban clients when an attack is over the specified ban threshold. For attack throttling clients will be banned after a specified number of repeated attacks.
Have a look at the change log for the full list of improvements and enhancements.
This release added support for automatic updates from phpids.org, this means you don’t have to wait for Mute Screamer to be updated to get the latest rules and converter for PHPIDS.
The update process will check phpids.org for changes to default_filter.xml and Converter.php. If an update is found it will be displayed on the Updates page in the WordPress admin.
As we are updating Mute Screamer core files we want to be very careful about what is to be updated. That is why when going through the update process you will be shown a diff of the changes to be applied to either default_filter.xml and/or Converter.php.
This lets you see exactly what is going to be changed and gives you a chance to review the changes to make sure they are legit. It was also a good excuse to use the diff engine included in WordPress that is used for comparing post revisions. As always have a backup of your site before running any updates.
