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

From Bruce Momjian
Subject Re: pgsql: Adjust user-facing documentation to explain why we don't check
Date
Msg-id 200702201840.l1KIeUi15934@momjian.us
Whole thread Raw
In response to Re: pgsql: Adjust user-facing documentation to explain why we don't check  (Magnus Hagander <magnus@hagander.net>)
Responses Re: pgsql: Adjust user-facing documentation to explain why we don't check
Re: pgsql: Adjust user-facing documentation to explain why we don't check
List pgsql-committers
Magnus Hagander wrote:
> Bruce Momjian wrote:
> > Andrew Dunstan wrote:
> >> Tom Lane wrote:
> >>> Log Message:
> >>> -----------
> >>> Adjust user-facing documentation to explain why we don't check pgpass
> >>> file permissions on Windows.
> >>>
> >> +On Microsoft Windows, the file is stored in a directory that is secure by
> >> +default, so no special permissions check is made.
> >>
> >>
> >>
> >> I doubt this is true if PGPASSFILE is set.
> >
> > I thought it would be in the user's Application Data directory, or are
> > you saying they might put it somewhere else?
> >
>
> 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?

--
  Bruce Momjian  <bruce@momjian.us>          http://momjian.us
  EnterpriseDB                               http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

pgsql-committers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: pgsql: Adjust user-facing documentation to explain why we don't check
Next
From: Magnus Hagander
Date:
Subject: Re: pgsql: Adjust user-facing documentation to explain why we don't check