note 66101 modified in function.eval by bjori
| From: | bjori@php.net | Date: | Mon, 15 May 2006 05:12:51 +0000 |
| Subject: | note 66101 modified in function.eval by bjori | ||
| References: | 1 | Groups: | php.notes |
| Request: | Send a blank email to php-notes+get-111295@lists.php.net to get a copy of this message | ||
Just as a reply to 'evildictaitor', eval() obfuscation can be of use use against script
kiddies, or people with little free time if implemented more intelligently.
And by more intelligently I mean more randomly, do perhaps a hundred iterations and randomly choose
the obfuscation method every iteration. Doing rot13 with base64 once, then something from Mcrypt()
and so on. Might take its toll on performance, but atleast isn't _that_ easily solved by
eval->print :)
Of course, obfuscation isn't really a way to securing your code, but might work if one's
in a hurry and doesn't have anything else better.
--was--
Just as a reply to 'evildictaitor', eval() obfuscation can be of use use against script
kiddies, or people with little free time if implemented more intelligently.
And by more intelligently I mean more randomly, do perhaps a hundred iterations and randomly choose
the obfuscation method every iteration. Doing rot13 with base64 once, then something from crypt()
and so on. Might take its toll on performance, but atleast isn't _that_ easily solved by
eval->print :)
Of course, obfuscation isn't really a way to securing your code, but might work if one's
in a hurry and doesn't have anything else better.
http://php.net/manual/en/function.eval.php