Skip site navigation (1) Skip section navigation (2)

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

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)postgresql(dot)org>, 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:40:30
Message-ID: 200702201840.l1KIeUi15934@momjian.us (view raw or flat)
Thread:
Lists: 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(at)momjian(dot)us>          http://momjian.us
  EnterpriseDB                               http://www.enterprisedb.com

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

In response to

Responses

pgsql-committers by date

Next:From: Magnus HaganderDate: 2007-02-20 18:43:43
Subject: Re: pgsql: Adjust user-facing documentation to explain why we don't check
Previous:From: Magnus HaganderDate: 2007-02-20 18:39:23
Subject: Re: pgsql: Adjust user-facing documentation to explain why we don't check

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group