Title: username_wp's Replies | WordPress.org --- # username_wp [ ](https://wordpress.org/support/users/username_wp/) * [Profile](https://wordpress.org/support/users/username_wp/) * [Topics Started](https://wordpress.org/support/users/username_wp/topics/) * [Replies Created](https://wordpress.org/support/users/username_wp/replies/) * [Reviews Written](https://wordpress.org/support/users/username_wp/reviews/) * [Topics Replied To](https://wordpress.org/support/users/username_wp/replied-to/) * [Engagements](https://wordpress.org/support/users/username_wp/engagements/) * [Favorites](https://wordpress.org/support/users/username_wp/favorites/) Search replies: ## Forum Replies Created Viewing 4 replies - 1 through 4 (of 4 total) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Look-See Security Scanner] No checks on suspicious function calls like "eval", "base64_decode", etc…?](https://wordpress.org/support/topic/no-checks-on-suspicious-function-calls-like-eval-base64_decode-etc/) * Thread Starter [username_wp](https://wordpress.org/support/users/username_wp/) * (@username_wp) * [10 years, 12 months ago](https://wordpress.org/support/topic/no-checks-on-suspicious-function-calls-like-eval-base64_decode-etc/#post-6425449) * Hi there, * I just had a look at the changes you made in the code: [https://plugins.trac.wordpress.org/changeset/1221011/look-see-security-scanner](https://plugins.trac.wordpress.org/changeset/1221011/look-see-security-scanner) * and… WOW :))) Thank you so much :))) * This definitely makes me want to test your plugin now! * I will indeed give you some feedback when I test it, please be patient because I am quite busy and have quite a few things to do before that. * Many thanks again and TTYS * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Look-See Security Scanner] No checks on suspicious function calls like "eval", "base64_decode", etc…?](https://wordpress.org/support/topic/no-checks-on-suspicious-function-calls-like-eval-base64_decode-etc/) * Thread Starter [username_wp](https://wordpress.org/support/users/username_wp/) * (@username_wp) * [11 years ago](https://wordpress.org/support/topic/no-checks-on-suspicious-function-calls-like-eval-base64_decode-etc/#post-6425384) * Hi there, * Thank you for your detailed answer and the grep command, useful workaround indeed. PHP is not supposed to be too lame at processing files and strings so how do you explain grep is so much faster than PHP for doing that? Aren’t there any ways you could optimize the code? I haven’t yet investigated all WP plugins which offer malware scanning (running locally on the server itself and not “in the cloud”) but a WP plugin like “antivirus” does this sort of things and has 100K + users so it seems and it’s not something completely impossible to achieve. * Maybe you could alleviate the performance and false positives impact by offering this functionality as an optional / separate feature where you could whitelist some directories / file extensions and also maybe switch off/on each (or a subset of) pattern to search? You could also output the time it takes to do the scan so the user can make the right trade off between performance / filtering strictness/ false positive ratio. * Obviously then it means providing these options would make the implementation a bit less easy but I guess you could deliver this in stages so as not to make it too bulky for you to do. * Obviously it’s completely up to you. Your plugin is already good as it is. I’m just a bit disappointed that it calls itself a “security scanner” but does not provide a way to actually scan for potentially dodgy code which is useful when you install / update a theme or plugin for example. * Sure a system grep could be used instead but it would make it less convenient/ integrated and it is also not multi-platform. It’s why WordPress plugins are made after all, because of the user-friendliness for WordPress users. * Any more thoughts on that? * Many thanks anyway and best regards * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Files Inspector] Why CRC32B rather than MD5 for example?](https://wordpress.org/support/topic/why-crc32b-rather-than-md5-for-example/) * Thread Starter [username_wp](https://wordpress.org/support/users/username_wp/) * (@username_wp) * [11 years ago](https://wordpress.org/support/topic/why-crc32b-rather-than-md5-for-example/#post-6404481) * Hi again, * Thank you for your positive response 🙂 * Obviously generating 2 hashes for each file might take longer / more resources than generating just one but I guess it makes it more secure and maybe will allow you to be backward compatible with the previous plugin versions. * In any cases as long as there are MD5 hashes then it ticks the box for me 🙂 * Many thanks again and I’m looking forward to your new version * Best regards * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Files Inspector] References to Akismet ?](https://wordpress.org/support/topic/references-to-akismet/) * Thread Starter [username_wp](https://wordpress.org/support/users/username_wp/) * (@username_wp) * [11 years ago](https://wordpress.org/support/topic/references-to-akismet/#post-6404480) * Hi, * Thank you for you answers and many thanks for the planned modifications 🙂 I’m already using another file monitoring plugin but once you’ve removed the Akismet references and added MD5 hashes then when I have some time I will try to test your plugin and if it’s very good then maybe you have a very good review from me coming your way 🙂 It’s always a plus to have a choice between different very good products so that would obviously be great if your plugin can be one of them 🙂 * Thank you again and TTYL Viewing 4 replies - 1 through 4 (of 4 total)