Re:Postgres: Boundless `Text` and Back Again
by kam on Friday September 10, 2021 @06:59PM
(#28487808)
What does string width have to do with SQL injection? You use parameterized queries, not just rely on your validation to reject quotes, right?
Re:Postgres: Boundless `Text` and Back Again
by iammisc on Saturday September 11, 2021 @12:18AM
(#28489396)
I do... Yes. I follow best practices like parameterized queries, string width validation, password hashing via memory intensive hash functions etc. These are all basic beat practices. When a company admits to not doing one, it makes me worry about the others.
This is the result of build fast and break things mentality which is toxic
One of the dangers in switching to high level languages is that people have lost any sense of data size. In C you almost always specify a max string width because that is the easiest easy to deal with strings. While C has many shortcomings, forcing the responsible programmer to deal with string width is a good thing.
Honestly as a stripe user, this sort of unvalidated input terrifies me. Stripe deals with money. All inputs ought to be validated. I figured the company would spend a lot of engineering time making sure data was cleaned and couldn't escape like this.
Today it's a string width issue. Tomorrow it's a sql injection. I'm surprised stripe let you publish this.