[DBTech] DragonByte Security 4.7.0

Update highlights

!!!This version requires PHP 7.4+!!!

This version improves the display shown to users when reviewing their login sessions, as the user agent is now parsed to display more human-readable information such as browser/version and operating system.

There is also new options to exclude users with Two-Factor Authentication enabled when performing batch user update actions from DB Security.

This version also refactors some backend code and fixes a compatibility issue with PHP 8.2 / 8.4.


Complete Change Log

Feature: Improved session information display, now parses browser and OS
Feature: Optionally exclude TFA-enabled users from batch update actions
Change: Refactored backend code
Change: Bump minimum PHP version to 7.4 and recommended version to 8.2
Change: Update dependencies to the latest version(s)
Fix: User agent is now updated for login sessions
Fix: Bad Behavior would run on PHP versions newer than it supports
Fix: Fix PHP 8.2 compatibility issues
Fix: Fix PHP 8.4 compatibility issue

Update highlights

This version fixes an issue where certain custom entries in the config.php file would produce a server error if the "Config Tamper" security watcher was enabled.


Complete Change Log

Fix: Fix Config Tamper watcher producing a server error when running on XenForo Cloud / with certain config.php additions

Update highlights

This version fixes an issue where an old, unused block of code could be used to delete other users' "Remember Me" records.


Complete Change Log

Fix: Fixed an issue where it was possible to delete other users' "Remember Me" records

Update highlights

This version fixes an issue where a server setup using replication could experience performance degradation on a guest's first visit.

Furthermore, an issue where the BadBehavior integration could cause a server error has been addressed.


Complete Change Log

Change: Improve compatibility with databases setup for replication
Fix: Fix "Constant BB2_CORE already defined" error in the Bad Behavior logs

Update highlights

This version changes some internal functions to no longer rely on deprecated XenForo functions, and fixes a server error that could occur with certain maliciously crafted URLs.


Complete Change Log

Change: Change UTF-8 related functions
Fix: Certain URLs could cause a server error in dispatcherPostRender

Update highlights

This version fixes an issue with "Always show CAPTCHA when logging in to: front-end" option if the login form was loaded via AJAX (i.e. in an overlay).


Complete Change Log

Fix: The "Always show CAPTCHA when logging in to: front-end" option would not function correctly if the login form was loaded via AJAX

Update highlights

This version fixes an issue wherein modifying the "Master Style", such as while upgrading add-ons, would attempt to send invalid emails when the "Email webmaster on template changes" option is turned on.

"Master Style" changes are no longer subject to email notifications.


Complete Change Log

Fix: Fix potential server error while upgrading other add-ons

Update highlights

This version fixes a couple of issues with the new Login Captcha feature, as well as an issue with the new Security Lock feature in XenForo 2.2.


Complete Change Log

Fix: "You must be logged in to do that" pages did not have captcha properly applied on first load
Fix: Fix incompatibility with 3rd party add-ons that also extend certain View classes
Fix: Using the new XF2 security locking feature in a Security Watcher could fail to apply the lock in certain scenarios

Update highlights

This version fixes an issue wherein the new Login Captcha feature could be enabled on pages that did not support it.


Complete Change Log

Fix: Login captcha no longer applies to password confirmation screens

Feature: Account unlocks now add an entry to the IP log
Feature: Batch update: Account lock (user unlock)
Feature: Optional forced CAPTCHA for front-end and AdminCP logins
Change: Account locks (user unlock or admin unlock) are now logged in the User Change Log
Fix: Fix potential server errors when viewing certain pages
Fix: Fix an issue where the User Information watcher wasn't correctly limiting to the field described in the Watcher Rules