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

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

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Dave Page <dpage(at)postgresql(dot)org>
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:04:00
Message-ID: 45DB5430.5060004@hagander.net (view raw or flat)
Thread:
Lists: pgsql-committers
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.

//Magnus


In response to

Responses

pgsql-committers by date

Next:From: Dave PageDate: 2007-02-20 20:06:34
Subject: Re: pgsql: Adjust user-facing documentation to explain why we don't check
Previous:From: Bruce MomjianDate: 2007-02-20 19:59:18
Subject: pgsql: Update "encode" documentation to mention that 'escape' only

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