acdc_rulz
Forum Replies Created
-
Tried this plugin and had some performance issues with it. Debugging the script showed the problem – this scanner does NOT handle large binary files or any binary files that are located in the WordPress directory structure for that matter. May have something to do with its call to file_get_contents when the file being passed is binary? Workaround was to temporarily move my files directory to another location and run the scanner again. Works great otherwise!
Forum: Plugins
In reply to: [Plugin: WordPress Exploit Scanner] Exploit Scanner not workingHello,
I had the same problem as portenkirchner above and could not find my php error log. I host my own blog and determined that the error log directory parameter in my php.ini was not set correctly. I fixed this and discovered when I ran the Exploit Scanner again that indeed I was getting an out of memory error in my php error log. However, the Exploit Scanner script does not return anything if this error occurs and all I would get is the same result “This script searches through your WordPress install for signs that may”…maybe this can be fixed in a future version to at least tell someone if there was a memory error???Here is the exact error from my php error log:
“[21-Oct-2009 11:40:42] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 51118080 bytes) in /www/xxxxxxx/wp-content/plugins/exploit-scanner/exploit-scanner.php on line 80
“
I corrected this by going into my wp-config.php per the README instructions and added the following:
define( ‘WP_MEMORY_LIMIT’, ‘256M’ );After doing this, the error went away but the Exploit Scanner now had a different problem. Now, when I started a scan, the “Please Wait while Loading” animated .gif would display for hours on end. After some painstaking debugging of the Exploit Scanner code, I determined the problem. It seems that the Exploit Scanner does not handle scanning binary files if they are anywhere in the WordPress directory structure. To fix this problem, I simply moved my “files” outside of the WordPress directory structure and voila, the scanner completed properly! Again, this should be fixed in a future version by either telling the user that the scanner does not work with binary files or build in intelligence to skip over these files/scan them in a different way.
Anyone have a similar problem using this script with binary files?
Thanks!