Banned Items

Version 2.0.0b2: - Developer: jrBanned_add_ban() and jrBanned_delete_ban() add and remove Banned Items from code, checked as the Banned Items forms check them Version 2.0.0b1: - New: "Banned Countries" global config options for banning country IP ranges (updated weekly from the five Regional Internet Registries) - New: Updated block checking code to be faster on larger systems - New: Banned IP Address entries can be a CIDR range (i.e. 123.125.0.0/16) - Change: whois lookup on the Banned IP list: modal title shows "whois lookup: " - Change: Updated Global Config and Tool tabs with new options - Change: The Banned IP Whois button opens the lookup in a modal window (a new tab on Jamroom Core versions before 7.1.0b1) - Change: "Blocked URL Strings" now match the start of a part of the URL path instead of anywhere in the URL, and the default list has been updated (sites still using the old default list are updated automatically) - Change: Re-adding an existing Banned Item now updates its Match Substring setting and note - Change: Banned IP Addresses are also checked on AJAX requests (most form submissions) - Bug Fix: Visitors were blocked when a Blocked URL String appeared anywhere in the URL, such as search result page links for "wp-admin" or item titles containing "wp-content" - Bug Fix: Banning a complete IP address also banned every address starting with it - banning 1.2.3.4 also blocked 1.2.3.40 to 1.2.3.49 - Bug Fix: Create Banned Item: the "would ban your IP address" check only caught an exact match of the whole entry, a trailing empty line gave an "invalid item value - please enter 113" error, and 1 character entries were accepted - Bug Fix: Blocked IPs tool did not show the last IP address on the last page - Bug Fix: Forbidden Words containing a "/" never matched - Developer: Updated unit tests with fixes and cleanups - Developer: The "banned_item_delete" event now includes the ban_id, ban_value and ban_partial of the deleted item Version 1.7.0; - New: Module updated to better support blocking of scanning bots using trap URLs - New: "Banned IP" tool to view IP addresses that have been auto blocked Version 1.6.2: - Change: Removed "Retry-After" header from 403 Forbidden response - Change: Banned item timeout cache key changed from 5 minutes to 60 minutes Version 1.6.1: - Bug Fix: Possible Activity Log error resetting banned item cache when auto ban is enabled Version 1.6.0: - New: "Auto Ban Blocked Requests" global setting that is used to enable auto-banning - Change: Updated view structure to support new updates in Jamroom Core 6.5.12+ Version 1.5.4: - New: "Enable in Forms" global config to enable/disable automatic form submission scanning Version 1.5.3: - New: "banned_item_create" Event trigger fired when a new banned item is created - New: "banned_item_delete" Event trigger fired when an existing banned item is deleted Version 1.5.2: - New: Create Banned Item form updated to allow creating multiple banned entries Version 1.5.1: - New: "Blocked URL Strings" config option to define strings to block in URLs - New: "Blocked User Agents" config option to block access by browser agent Version 1.5.0: - New: "Enable Blocking" config option to block server scanners for wordpress, phpMyAdmin, etc. - Change: Exclude existing profile/user names and emails from banned text check Version 1.4.0: - New: Option added to select word or partial seaches for banned names, emails and words Version 1.3.6: - Change: Updated to prevent the local server IP address from being banned Version 1.3.5: - Change: Admin Note for a banned item entry now opens in a modal window when clicked Version 1.3.4: - Bug Fix: Banned items may not show as banned when using the Test Items tool Version 1.3.3: - New: Admin note can be added when adding a ban to help keep track of why the ban is there Version 1.3.2: - Bug Fix: Banned Items not being deleted during Developer Tools system reset Version 1.3.1: - Bug Fix: Some "name" banned items could get used as "word" banned items Version 1.3.0: - New: Support for modules to register "banned_type" support for custom ban functions Version 1.2.1: - Change: Banned words must be at least 2 characters in length - Bug Fix: Multi-byte banned words may not be caught as substring of string Version 1.2.0: - New: Banned Item check runs on all text fields by default (no more requiring module config) - New: Searches that include banned words result in no items found for non-admin users Version 1.1.3: - Bug Fix: Item Value error when entering certain characters for a banned name Version 1.1.2: - Bug Fix: "word" boundaries added in 1.1.1 may not work properly on HTML string Version 1.1.1: - Change: "word" banned items no longer match substrings of longer words - Bug Fix: Searching in the Banned Items browser was resulting in a 404 not found page Version 1.1.0: - New: "Test Items" tool will test a value against currently configured banned items - Change: Partial IP Addresses can now be entered as Banned Items Version 1.0.3: - New: Support added for banning email addresses and email domains Version 1.0.2: - New "Banned Items" tab in ACP that is the default view for the module Version 1.0.1: - Update error message for banned IP to use jrCore_notice() Version 1.0.0: - Initial Release