note 66101 added to function.eval

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. ---- Server IP: 212.47.220.13 Probable Submitter: 213.35.234.193 ---- X-Spam-Status: No, hits=3.1 required=5.0 tests=DATE_MISSING,FROM_NO_LOWER autolearn=no version=2.64 ---- Manual Page -- http://www.php.net/manual/en/function.eval.php Edit -- http://master.php.net/note/edit/66101 Del: integrated -- http://master.php.net/note/delete/66101/integrated Del: useless -- http://master.php.net/note/delete/66101/useless Del: bad code -- http://master.php.net/note/delete/66101/bad+code Del: spam -- http://master.php.net/note/delete/66101/spam Del: non-english -- http://master.php.net/note/delete/66101/non-english Del: in docs -- http://master.php.net/note/delete/66101/in+docs Del: other reasons-- http://master.php.net/note/delete/66101 Reject -- http://master.php.net/note/reject/66101 Search -- http://master.php.net/manage/user-notes.php