News for hackers. Stuff that matters.
Re:Be Careful with Python's New-Style String Format by peller on Saturday December 31, 2016 @05:12PM (#13293475)
Isn't SQL injection caused by ingesting raw user input though?

Seems to me you always have to be careful with user-supplied data.

Re:Be Careful with Python's New-Style String Format by halomru on Saturday December 31, 2016 @06:47PM (#13293827)
I would have said that SQL injection is caused by emitting unescaped user input to your SQL server
Re:Be Careful with Python's New-Style String Format by tlrobinson on Saturday December 31, 2016 @07:06PM (#13293923)
If I call eval(string) am I emitting unescaped user input to the eval function?

I guess the definition of "injest" here is reading bytes off the wire?

Re:Be Careful with Python's New-Style String Format by john_reel on Saturday December 31, 2016 @10:45PM (#13294632)
If string is unescaped user input, then yes, you are.
Re:Be Careful with Python's New-Style String Format by meowface on Saturday December 31, 2016 @05:31PM (#13293563)
"Ingesting raw user input is good if you only use it to interface with other systems that provide a way to separate data from instructions or at least escape strings."
Re:Be Careful with Python's New-Style String Format by foolfoolz on Saturday December 31, 2016 @05:37PM (#13293589)
sql injection is commonly caused by combining your query with its related data parameters in unsafe ways. you are emitting raw user input you received to another program, the database, it's your responsibility to give this to the DB safely.

you still have to be careful, and when you follow all the right best practices you can safely ingest raw user input.

I've worked at a company that escaped user input before inserting into the DB. it's a horrible nightmare I don't think anyone should have to experience.