Securitycheck Pro for WordPress 2.4.2 released

I have updated Securitycheck Pro for WordPress to version 2.4.2 to fix some bugs and add improvements:
+ Hardened the firewall's activation logic to make sure protection is enabled by default on installations where it had never been explicitly toggled
+ Added a connection timeout to the reply a managed site sends back to Control Center, so connection issues are now logged instead of failing silently
+ Fixed the "Is backend protection enabled?" status check never detecting a correctly configured admin password protection
+ Fixed "HTTP Headers Protection" status requiring optional policy fields to be filled in, even when the site legitimately doesn't use them
+ Replaced the "Disable server signature" status check (which could never be satisfied on this platform) with a "Disable XML-RPC" check
+ Fixed the security score never being able to reach a clean 100%
+ Added a "Number of items per page" option (Screen Options panel, top right) to the File Manager, File Integrity, Malware Scanner and Web Firewall Logs listings, each remembered independently
+ Fixed the Web Firewall Logs read/unread filter getting stuck after using the search filters (or the "Clear filters" button), which could make newly logged attacks disappear from the list until the filter was manually reset
+ Fixed remote tasks sometimes not being picked up promptly by a managed website (especially on sites using page caching) by having the website trigger its own background check immediately after receiving a task, instead of relying solely on Control Center's follow-up visit
+ Fixed the scan/task logs folder not receiving its server-level protection file due to a file path bug, and added automatic self-repair for existing installations; also upgraded that protection rule to a version compatible with both older and newer Apache configurations

Special thanks to Simon for his time and patience testing these fixes and reporting them in such detail.

Regards,
Jose