From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Curt Sampson <cjs(at)cynic(dot)net> |
Cc: | Doug McNaught <doug(at)wireboard(dot)com>, "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: psql and passwords |
Date: | 2002-04-16 03:34:43 |
Message-ID: | 200204160334.g3G3YhH04170@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Curt Sampson wrote:
> On 15 Apr 2002, Doug McNaught wrote:
>
> > "Nigel J. Andrews" <nandrews(at)investsystems(dot)co(dot)uk> writes:
> >
> > > Anyway, the solution is to set PGPASSWORD in the evironment. Once I
> > > remembered about that it all became so much easier.
> >
> > Note that this is potentially insecure as some systems expose your
> > environment to other users.
>
> Indeed. What about adding an option whose argument is the name of
> a file containing the password?
Already on TODO and I hope it is done for 7.3:
* Add PGPASSWORDFILE environment variable or ~/.pgpass to store
user/host/password combinations
We even have:
* Remove PGPASSWORD because it is insecure on some OS's
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | postgres | 2002-04-16 04:42:57 | 'cluster' messes up a table |
Previous Message | Curt Sampson | 2002-04-16 03:32:43 | Re: psql and passwords |