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

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

From: Dave Page <dpage(at)postgresql(dot)org>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, 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 20:06:34
Message-ID: 45DB54CA.7030906@postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Magnus Hagander wrote:
> Dave Page wrote:
>> Magnus Hagander wrote:
>>> It would break insofar that it wouldn't work. the pgpass file. It will
>>> of course not break *windows*, but people will consider PostgreSQL broken.
>>>
>> Please explain why it won't work. *Existing* pgpass files would need to
>> be secured, but that could be handled with documentation and suitable
>> checks and hints in pgAdmin/libpq. New pgpass files created by pgAdmin
>> (or other apps) would simply need to be secured by those apps at
>> creation time.
> 
> Files created using notepad (or whatever) will not work. Unless you
> manually fiddle around with the permissions.

If you are savvy enough to read the docs, un-hide the directory, and
manually create the file in the correct format, surely you can also run
cacls on it? We expect *nix users to run chmod on theirs after all.

I don't see this as such a big issue.

Regards, Dave.

In response to

Responses

pgsql-committers by date

Next:From: Andrew DunstanDate: 2007-02-20 20:30:29
Subject: Re: pgsql: Adjust user-facing documentation to explain why we don't check
Previous:From: Magnus HaganderDate: 2007-02-20 20:04:00
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