From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Ow Mun Heng <ow(dot)mun(dot)heng(at)wdc(dot)com> |
Cc: | Tommy Gildseth <tommy(dot)gildseth(at)usit(dot)uio(dot)no>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Best way to "mask" password in DBLINK |
Date: | 2009-08-12 07:56:17 |
Message-ID: | 9837222c0908120056k5e834d52i32790b58b5af4fc4@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Aug 12, 2009 at 09:30, Ow Mun Heng<ow(dot)mun(dot)heng(at)wdc(dot)com> wrote:
>
>
> -----Original Message-----
> From: Tommy Gildseth [mailto:tommy(dot)gildseth(at)usit(dot)uio(dot)no]
>
> Ow Mun Heng wrote:
>>> I'm starting to use DBLink / DBI-Link and one of the "bad" things is that
>>> the password is out in the clear.
>>> What can I do to prevent it from being such? How do I protect it from
>>> 'innocent' users?
>
>>If I'm not mistaken, it's possible to put your password in the .pgpass
>>file in the postgres-users home folder, on the server where the postgres
>>cluster is running.
>
> Isn't that how one connects using the CLI? Eg: via psql?
You need to put it in the .pgpass file of the postgres user - the one
that runs the server. .pgpass is dealt with by libpq, and DBLink and
DBI-Link both use libpq to connect to the remote server.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2009-08-12 08:01:11 | Re: NOTICE: there is no transaction in progress |
Previous Message | Tommy Gildseth | 2009-08-12 07:49:02 | Re: Best way to "mask" password in DBLINK |