Re: Best way to "mask" password in DBLINK

From: Tommy Gildseth <tommy(dot)gildseth(at)usit(dot)uio(dot)no>
To: Ow Mun Heng <ow(dot)mun(dot)heng(at)wdc(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Best way to "mask" password in DBLINK
Date: 2009-08-12 07:49:02
Message-ID: 4A8273EE.60504@usit.uio.no
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Ow Mun Heng 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?
>
> My connection string looks like this.
>
> SELECT aaa
> FROM dblink('dbname=hmxmms host=xxx.xxx.xxx.xxx user=yyy
> password=zzz'::text, 'SELECT * from tablename'::text) b4(aaa xxx );
>
> I've placed the above as a view hence the user/pass is being hardcoded(?) of
> sorts

Just leave out the "password=zzz" part of the connection string.

--
Tommy Gildseth

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Magnus Hagander 2009-08-12 07:56:17 Re: Best way to "mask" password in DBLINK
Previous Message Xharon 2009-08-12 07:34:35 Re: Updating a specific number of rows in pl/pgsql