Randem Systems Support Board

BotBanish Versions Prior to 2.2.x Have Been Discontinued as of December 31, 2017 and will no longer work. If you have a BotBanish version prior to 2.2.x, please download the newest version from http://botbanish.com, uninstall the old version then install the new version. If you have purchased an APIKEY you will need to change it in the Settings_Client.php file or you will be using the free version.

02/24/2018 - Version 2.2 Build 6

FIX: Database Error: Unknown column 'diag' in 'field list' appears in the SMF error log. This column is for a future client release that the current server supports. It has been accounted as to not cause an error condition. Error was caused from a BotBanish server update.

02/04/2018 - Version 2.2 Build 5

URGENT!

FIX: When an @ sign was detected in the user agent of a bot attempting to attack the system a entry in the .htaccess file was recorded with a cr/lf in the entry causing a error 500 error page stopping access to the website.

Invalid entry would look like this:


SetEnvIfNoCase User-Agent "webauth
cmcm.com." bad_bot


When the entry should look like this:


SetEnvIfNoCase User-Agent "webauth@cmcm.com." bad_bot


02/02/2018 - Version 2.2 Build 4

FIX: Fixed errors that were being recorded in the database but not affecting operations.

01/17/2018 - Version 2.2 Build 3

FIX: Full user agent was being recorded in the .htaccess when hit count abuse or a hidden bot was detected, which would deny any further users with the same user agent from accessing the site.

URGENT!

Check your root .htacces file for entries with the full user agent and remove these entries from the .htaccess file. Such as (example only):

SetEnvIfNoCase User-Agent "mozilla/5.0 (macintosh; intel mac os x 10.12; rv:52.0) gecko/20100101 firefox/52.0" bad_bot

A good entry will look more like this:

SetEnvIfNoCase User-Agent "wotbox" bad_bot

NEW -  [SMF ONLY]: Added Post Protection (Comment) so that if a users username and/or email is listed in our database as a spammer, they will be locked out when attempting to post a message.

FIX: Escaped user-agents in SQL statement. Sometimes the user-agents has special characters in them and would fail on database inserts.

NEW -  [SMF ONLY]: After a successful login the users IP will be removed from being blocked until a new logon attempt is started with that IP

URGENT!

FIX: If the BotBanish server cannot be reached for any reason (timeouts, no internet connection etc...) Botbanish Client will continue to work but bot lockouts cannot be processed until a connection to the BotBanish server can be re-established.
__________________________________________________________________________________________