From: Rick Roman <rick@cotse.net>
To: pgsql-admin@postgresql.org
Subject: Preventing sql injection
Date: Wed, 10 Aug 2005 10:02:05 -0700
Message-ID: <42FA330D.7020908@cotse.net> (raw)
I have a web application that will allow users to submit comments. The
database activity consists of a single insert statement into a comments
table. I want to lock down this operation against sql injection attacks.
Can someone point me to a discussion of general principles? I've seen
reference to V3 extended-query protocol. Where is this invoked? Other
suggestions?
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: rick@cotse.net
Subject: Re: Preventing sql injection
In-Reply-To: <42FA330D.7020908@cotse.net>
References: <42FA330D.7020908@cotse.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox