Comments for MIKESTOWE.COM

Comment on User First… Not Mobile First by mike

mike — Wed, 18 Apr 2012 21:45:17 +0000

This works well if using responsive imports verses responsive conditions in the stylesheet, but you still run into the issue of space and feature compatibility overall. There’s also the issue of how much content and data is being used, again depending on the site, as well as if the content meets the expectations of the user, as their expectations often vary with the device they are using.

Comment on User First… Not Mobile First by Mike Willbanks

Mike Willbanks — Wed, 18 Apr 2012 21:32:34 +0000

One word; media queries

Comment on Simple jQuery AutoComplete Script by Edgaras

Edgaras — Wed, 11 Apr 2012 09:54:17 +0000

Hi, Mike, fix here: ” if($(‘#’+id).val().length > autosuggest_min_length) {”

I think, that is how it supposed to be :

“if($(‘#’+id).val().length >= autosuggest_min_length) {“

Comment on PHP Malicious Code Scanner by mike

mike — Tue, 28 Feb 2012 16:36:38 +0000

Hey Nico,
I’ve updated the script on GitHub to fix that issue and also fix some issues in PHP 5.4

Thanks,
Mike

Comment on PHP Malicious Code Scanner by Nico

Nico — Fri, 24 Feb 2012 15:19:37 +0000

hello, with the file from GitHub I have this errors:

Warning: scandir(__DIR__) [function.scandir]: failed to open dir: No such file or directory in /home/…/public_html/malscan.php on line 35

Warning: scandir() [function.scandir]: (errno 2): No such file or directory in /home/…/public_html/malscan.php on line 35

Fatal error: Uncaught exception ‘Exception’ with message ‘Unable to scan directory __DIR__. Please make sure proper permissions have been set.’ in /home/…/public_html/malscan.php:38 Stack trace: #0 /home/…/public_html/malscan.php(28): phpMalCodeScan->scan(‘__DIR__’) #1 /home/…./public_html/malscan.php(76): phpMalCodeScan->__construct() #2 {main} thrown in /home/…./public_html/malscan.php on line 38

Comment on PHP Malicious Code Scanner by mike

mike — Wed, 18 Jan 2012 22:19:30 +0000

Joseph – I have updated the script on GitHub. Can you check that out and see if it works for you?

Comment on PHP Malicious Code Scanner by mike

mike — Wed, 18 Jan 2012 22:18:38 +0000

I have updated the script on GitHub. Can you check that out and see if it works for you?

Comment on PHP Malicious Code Scanner by mike

mike — Wed, 18 Jan 2012 21:57:39 +0000

Many applications contain vulnerabilities that allow for users to upload files via back-doors in the code. This is most commonly done by spam-bots on applications such as WordPress and OSCommerce. The purpose of this application is not to prevent these leaks, but rather to help identify when a leak has been exploited. This script is designed to send a red flag notifying the developer that a malicious file has indeed been uploaded through a scripting backdoor and that it should be promptly dealt with, and the script should be reviewed to close any security gaps.

Comment on PHP Malicious Code Scanner by Asad

Asad — Wed, 18 Jan 2012 21:50:52 +0000

Well its dumb to assign untrusted users with input filters that allow them to input php code that can be run on the server. That is why people that use drupal should make sure they don’t use php filter unless they absolutely need it. Other than that if your solution requires sharing of source code there are plenty of options such as Google Code, GIT, SVN, etc. to make sure what the users are uploading cannot be executed on ur production server.

Comment on PHP Malicious Code Scanner by mike

mike — Mon, 16 Jan 2012 14:55:45 +0000

Thanks – I will take a look at this and get it fixed.