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

Re: PGPASSWORD

From: postgresbugs <postgresbugs(at)grifent(dot)com>
To: Oliver Jowett <oliver(at)opencloud(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: PGPASSWORD
Date: 2005-02-26 13:56:33
Message-ID: 42208011.4090100@grifent.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Oliver Jowett wrote:

> postgresbugs wrote:
>
>> The functionality provided by PGPASSWORD should not be removed unless 
>> there is a functionality other than .pgpass, which is fine for some 
>> uses and not for others, that will provide similar functionality. 
>> That could be psql and pg_dump and the like accepting a password on 
>> the command line as I stated earlier. 
>
>
> Putting the password on the command line would be even more of a 
> security problem than PGPASSWORD is now. I agree that an alternative 
> to ,pgpass would be useful, but it needs to be a *secure* alternative.
>
> -O

That may be true. Again, I think the option to use or not use PGPASSWORD 
or something similar should be up to the system administrator.

John Griffiths

In response to

pgsql-bugs by date

Next:From: postgresbugsDate: 2005-02-26 15:06:22
Subject: Re: PGPASSWORD
Previous:From: Sergey KoshcheyevDate: 2005-02-26 13:09:39
Subject: Re: BUG #1470: Boolean expression index not used when it could be

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