From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Christophe Dore <c(dot)dore(at)castsoftware(dot)com>, rod <rod(at)iol(dot)ie>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: prevent connection using pgpass.conf |
Date: | 2010-04-13 00:30:34 |
Message-ID: | 201004130030.o3D0UY907727@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Magnus Hagander wrote:
> 2010/4/1 Christophe Dore <c(dot)dore(at)castsoftware(dot)com>:
> >
> > - is there any configuration that can be done on server side to prevent
> > the client side to use such file to read passwords ?
>
> No. It happens before the user ha slogged in, obviously.
>
>
> > - is there any options that can be set in postgres libpq C library to
> > prevent the connection functions to search for password in files ?
>
> No, but you could possibly set the PGPASSFILE environment variable to
> a place where you *know* there won't be a pgpass file, if you can
> determine such a place.
/dev/null?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | John R Pierce | 2010-04-13 00:36:54 | Re: prevent connection using pgpass.conf |
Previous Message | jimmy Zhang | 2010-04-13 00:30:06 | [ANN]VTD-XML 2.8 |