Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explain why tainted data is bad #8

Open
petdance opened this issue Aug 30, 2011 · 0 comments
Open

Explain why tainted data is bad #8

petdance opened this issue Aug 30, 2011 · 0 comments

Comments

@petdance
Copy link
Owner

From Steve Davis steved@vis.id.au

Hey Andy,

Thanks for your bobby-tables page and language examples.

I see your todo list includes “explain why creating code from outside data is bad” and am wondering when you are going to get to that.

I definitely understand the problem of SQL injection having had one of my early sites injected and then a crude “pay me or I will show you more of your data” attempt. However I don’t understand “why creating code from outside data is bad” or even what you mean exactly.

So a rundown on the whole thing and how pg_query_params prevents injection would be excellent.

Thanks in advance

All the best

Steve

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant