| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Christophe Dore <c(dot)dore(at)castsoftware(dot)com> |
| Cc: | rod <rod(at)iol(dot)ie>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: prevent connection using pgpass.conf |
| Date: | 2010-04-01 09:57:37 |
| Message-ID: | t2h9837222c1004010257tf835e2a6pd2e08c627b3f6d14@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alban Hertroys | 2010-04-01 10:01:30 | Re: Re : Re : Re : Re : Select in temporary table |
| Previous Message | Dave Page | 2010-04-01 09:55:15 | Re: "1-Click" installer problems |