No :) If you are really worried about these kind of attacks, I suggest you read one of the many articles that explains how to write a secure PHP application.
You can also take it further and write a "user input" filter using the framework that Rasmus added for this purpose (mostly from a XSS point of view, but you could apply it to SQL injection also). Lets kill this thread, as it is not an internals@ matter. --Wez. On Thu, 14 Aug 2003, Steven Brown wrote: > php.net has some sort of failsafe it seems if you try and add another > semicolon, "BAD HACKER!! No database cracking for you today!", hee, but > you have to concede how easy it is to not properly check user input that > makes it into a query. That took me all of 15 minutes to find. It's > hard to find a large PHP-based site that doesn't have at least one such > bug, php.net included. > > It's an obvious argument for not adding unsafe functionality when you > don't have to, isn't it? :) -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
