Re: [GENERAL] Postgres CGI Security Problem

Maarten Boekhold <maartenb@dutepp2.et.tudelft.nl>

From: Maarten Boekhold <maartenb@dutepp2.et.tudelft.nl>
To: Dustin Sallings <dustin@spy.net>
Cc: "Shawn T. Walker" <swalker@iac.net>, Chris Hardie <chris@summersault.com>, pgsql-general@postgreSQL.org
Date: 1998-08-10T07:21:42Z
Lists: pgsql-general
On Sun, 9 Aug 1998, Dustin Sallings wrote:

> > > Chris Hardie writes:
> > >  > In anycase, I'm using the Postgres.pm module with PERL, and it doesn't
> > >  > seem to support the passing of a username/password pair (correct me if
> > >  > I'm wrong) from a CGI script.  I'll attempt to code that, unless
> > >  > someone has done it already.
> > 
> > Actually Pg.pm *does* allow you to connect with a username/password. If
> > you use the 'new-style' methods of Pg.pm, do $db->connect("dbname=..
> > user=.. password=..");. If you use the 'old-style' (like I do), use
> > PQconnectdb()  with the same arguments.
> 
> 	He said Postgres.pm, not Pg.pm.  There are three modules (that I've
> used anyway) to do Postgres connectivity via perl:
> 
> 	Pg.pm       (ugly, too C like for perl)
> 	Postgres.pm (very perl like)
> 	DBD::Pg     (best way to go, very similar to Postgres.pm)

Ah, I didn't know if any Postgres.pm, so I assumed he ment Pg.pm. I've 
seen ppl making that mistake several times (saying Postgres.pm when they 
ment Pg.pm).

Maarten

_____________________________________________________________________________
| TU Delft, The Netherlands, Faculty of Information Technology and Systems  |
|                   Department of Electrical Engineering                    |
|           Computer Architecture and Digital Technique section             |
|                          M.Boekhold@et.tudelft.nl                         |
-----------------------------------------------------------------------------