| From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
|---|---|
| To: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
| Cc: | postgresbugs <postgresbugs(at)grifent(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: PGPASSWORD |
| Date: | 2005-02-27 11:16:47 |
| Message-ID: | 4221AC1F.9020600@opencloud.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Andreas Pflug wrote:
> 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.
>
> The command line could take a file handle of an inherited pipe.
Yeah, that's what I originally suggested. Tom didn't seem to like it
though..
-O
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Hallgren | 2005-02-27 11:20:11 | Re: BUG #1502: hash_seq_search might return removed entry |
| Previous Message | Andreas Pflug | 2005-02-27 10:53:01 | Re: PGPASSWORD |