Re: When to encrypt
| От | dom@happygiraffe.net (Dominic Mitchell) | 
|---|---|
| Тема | Re: When to encrypt | 
| Дата | |
| Msg-id | 20041206095805.GA50010@ppe.happygiraffe.net обсуждение исходный текст | 
| Ответ на | Re: When to encrypt (Greg Stark <gsstark@mit.edu>) | 
| Список | pgsql-general | 
On Sun, Dec 05, 2004 at 11:31:34PM -0500, Greg Stark wrote:
> Derek Fountain <dflists@iinet.net.au> writes:
> > If another SQL Injection vulnerability turns up (which it might, given the
> > state of the website code),
>
> You will never see another SQL injection vulnerability if you simply switch to
> always using prepared queries and placeholders. Make it a rule that you
> _never_ interpolate variables into the query string. period. No manual quoting
> to get right, no subtle security audit necessary: If the SQL query isn't a
> constant string you reject it.
Another good piece of defense is mod_security (assuming that your web
server is Apache).  You can teach it about SQL injection attacks with a
little work.
    http://www.modsecurity.org
-Dom
		
	В списке pgsql-general по дате отправления: