[sivaganeshk]

Originally Posted by DragonByte Tech

It's what has to be done, unfortunately.

The error is not with vBSecurity, it's working as intended

You can turn off the notification for config.php variable tampering of course, but that would reduce the security of your forum, especially considering you already have one security breach going on (the tampering you keep getting notifs for).


Fillip

Hmm.. I understand. I had been using vbSecurity for 4 months.
Haven't got this issue until I started using Memcached and changed the datastore settings in config.php

May be, vbSecurity stored old config content , checks new config content and raises the notification.