pg.ddx.io  pgsql-php@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Rod Taylor <rbt@rbt.ca>
To: Davi Leal <davileal@terra.es>
Cc: pgsql-php@postgresql.org
Cc: web-dev@gnuherds.org
Subject: Re: postgreSQL web form; Security
Date: 18 Jul 2003 22:16:25 -0400
Message-ID: <1058580984.55079.10.camel@jester> (raw)
In-Reply-To: <200307142110.14069.davileal@terra.es>
References: <200307132144.02772.davileal@terra.es>
	<20030713200102.GA15127@wilbur.25thandClement.com>
	<200307142110.14069.davileal@terra.es>

> How can we avoid this security risk using PHP & postgreSQL?.

Be sure to verify all input from the untrusted source is valid, and
after you do that, be sure to escape it using pg_escape_string() or
pg_escape_bytea().

Attachments:

  signature.asc (application/pgp-signature, 186B) download

view thread (4+ messages)  latest in thread

Message-ID: <1058580984.55079.10.camel@jester>
Permalink:  ../1058580984.55079.10.camel@jester/
Also on:    postgresql.org/message-id/1058580984.55079.10.camel@jester

 · 

reply

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: rbt@rbt.ca, davileal@terra.es, web-dev@gnuherds.org
  Subject: Re: postgreSQL web form; Security
  In-Reply-To: <1058580984.55079.10.camel@jester>
  References: <200307132144.02772.davileal@terra.es> <20030713200102.GA15127@wilbur.25thandClement.com> <200307142110.14069.davileal@terra.es> <1058580984.55079.10.camel@jester>

* 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