News for hackers. Stuff that matters.
Re:Show HN: Big List of Naughty Strings for testing user-inp... by efriese on Monday August 10, 2015 @12:24PM (#10035617)
Yeah, I would make the SQL injection and command injections test a little less kinetic =). Using a simple SELECT test, like SELECT @@VERSION, would be a little safer... Edit: Forget to say thanks! This is a pretty cool list.
Re:Show HN: Big List of Naughty Strings for testing user-inp... by bryanlarsen on Monday August 10, 2015 @01:58PM (#10036157)
You want something that modifies so that you can detect that the SQL executed. But an INSERT would be a much friendlier than a DROP TABLE. :)
Re:Show HN: Big List of Naughty Strings for testing user-inp... by efriese on Monday August 10, 2015 @04:46PM (#10037164)
Not necessarily. If you do a test with good SQL and a second test with SQL Injection and compare the responses that can show SQL Injection exists without having to change the database. This won't work for all SQL injection tests, but I would rather take this approach first.