Re: pgsql: Adjust user-facing documentation to explain why we don't check

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Adjust user-facing documentation to explain why we don't check
Date: 2007-02-20 18:43:47
Message-ID: 13681.1171997027@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Magnus Hagander wrote:
>> PGPASSFILE takes a full path name, so you can put the file anywhere you
>> want. Just like on Unix.

> OK, so we _do_ need to check the permissions on pgpass on Win32, but we
> just don't know how to do that?

We could ignore PGPASSFILE on Windows, or restrict it to be in the
secure directory ...

regards, tom lane

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Andrew Dunstan 2007-02-20 18:44:10 Re: pgsql: Adjust user-facing documentation to explain why we don't check
Previous Message Magnus Hagander 2007-02-20 18:43:43 Re: pgsql: Adjust user-facing documentation to explain why we don't check