From: Ed Finkler <coj@cerias.purdue.edu>
To: Bruno Wolff III <bruno@wolff.to>
To: pgsql-php@postgresql.org
Subject: Re: Effectiveness of pg_escape_string at blocking SQL injection attacks
Date: Fri, 27 May 2005 11:06:27 -0500
Message-ID: <42974583.10207@cerias.purdue.edu> (raw)
In-Reply-To: <20050527155922.GA3930@wolff.to>
References: <4297435C.20605@cerias.purdue.edu>
<20050527155922.GA3930@wolff.to>
Bruno Wolff III wrote:
> The best advice is to use bind parameters rather than trying to build
> SQL strings consisting partly of user input.
That's good advice, but I suspect not everyone is going to know this,
and will have a tendency to use the escaping function to try and clean
intput. Do you have any suggestions about improving the security of the
pg_escape_string function?
--
Ed Finkler
Web and Security Archive Administrator
CERIAS - Purdue University
http://www.cerias.purdue.edu/
v: 765.496.6762 f: 764.496.3181
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-php@postgresql.org
Cc: coj@cerias.purdue.edu, bruno@wolff.to
Subject: Re: Effectiveness of pg_escape_string at blocking SQL injection attacks
In-Reply-To: <42974583.10207@cerias.purdue.edu>
References: <4297435C.20605@cerias.purdue.edu> <20050527155922.GA3930@wolff.to> <42974583.10207@cerias.purdue.edu>
* 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