I was just thinking how the developer of kbin made a post regarding a similar bug in kbin and some people made fun of him for missing something so obvious, and here we are 🤨
If you are creating some software in 2023, it should not be vulnerable to SQL injection.
There’s no “but” or “unless”.
I really wished the presentation layer and session management had that kind of clear interfaces, instead we are stuck into only solving some 99.9% of CSS and 90% of CSRF. But SQL injection is 100% complete solved for good.
Suddenly, very relatable today…
I was just thinking how the developer of kbin made a post regarding a similar bug in kbin and some people made fun of him for missing something so obvious, and here we are 🤨
There’s only two kinds of people:
Foolproofness is an asymptote. It’s not achievable but we can always get closer.
I think everyone is on a journey from 2 -> 1, some just get there sooner than others :)
If you are creating some software in 2023, it should not be vulnerable to SQL injection.
There’s no “but” or “unless”.
I really wished the presentation layer and session management had that kind of clear interfaces, instead we are stuck into only solving some 99.9% of CSS and 90% of CSRF. But SQL injection is 100% complete solved for good.