Re:“I've had to relearn coding to get through the new interv...
by alltakendamned on Friday December 04, 2020 @12:12AM
(#25299228)
Damn that SQL injection will get you owned in 3 seconds or less :D
[ Parent
| on HN ]
Re:“I've had to relearn coding to get through the new interv...
by aurbano on Friday December 04, 2020 @01:11AM
(#25299545)
It really really sucks that it’s almost 2021 and we still have to try to sneak in a little SQL injection just to see if they know about it...
Ffs is that never going to go away?
Re:“I've had to relearn coding to get through the new interv...
by jolux on Friday December 04, 2020 @01:42AM
(#25299683)
the only way it could possibly go away for good is database libraries that don’t support dynamic SQL. But you almost always need the flexibility at some point, and SQL is so powerful that taking it off the table is hard to justify.
Re:“I've had to relearn coding to get through the new interv...
by alltakendamned on Friday December 04, 2020 @04:00AM
(#25300385)
just use prepared statements instead of string concantenation to build your SQL statements.
Re:“I've had to relearn coding to get through the new interv...
by SamuelAdams on Friday December 04, 2020 @10:39AM
(#25303449)
Yes, there's lots of ways to fix SQL injection. I'm more surprised that after knowing about this vulnerability for 20+ years, its STILL lost on many developers. You and I pick up on it immediately, but there's (apparently) a lot of developers who think the code is "good enough, works for me" and ship it to production.
So it needs to be asked for in interviews, and if you find it and discuss it you're apparently one of the "better" programmers. The bar for being a passable programmer is literally on the floor.