News for hackers. Stuff that matters.
Re:Don’t try to sanitize input, escape output (2020) by marcosdumay on Thursday January 13, 2022 @12:03PM (#29923239)
If the user says his name is "Bob'; drop tables students --", that is what you should store on your database. Unless, of course it's not a valid name for the rest of the system.

That's so old and obvious advice that I'm surprised people keep posting here and upvoting. And even more surprised when people keep disagreeing here.

Re:Don’t try to sanitize input, escape output (2020) by ehutch79 on Thursday January 13, 2022 @12:19PM (#29923523)
If you're storing "Bob'; drop tables students --" in the database, you had to have sanitized your inputs, or there would be no students table.

The article title says NOT to sanitize inputs. perhaps it's that nuance doesn't fit in a headline, but eh...

Re:Don’t try to sanitize input, escape output (2020) by wvenable on Thursday January 13, 2022 @12:30PM (#29923711)
The confusion is what is input and what is output. The string "Bob'; drop tables students --" should not be sanitized/encoded on *input* to the application. However, if you're not using parameterized queries, it should be encoded on *output* to the database.

Data should only be sanitized in transit and not stored in an sanitized form. That's what the article is really saying.

Re:Don’t try to sanitize input, escape output (2020) by IshKebab on Thursday January 13, 2022 @01:59PM (#29925060)
No you don't. You use a parameterized query: execute("INSERT INTO foo VALUES (?)", user_input)