Re: prevent connection using pgpass.conf

From: Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl>
To: John R Pierce <pierce(at)hogranch(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: prevent connection using pgpass.conf
Date: 2010-04-13 09:57:52
Message-ID: 21C6F383-CDF9-4799-87AB-A194E2923F0D@solfertje.student.utwente.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 13 Apr 2010, at 2:36, John R Pierce wrote:

> Alban Hertroys wrote:
>> Storing those passwords encrypted on the client side seems the proper way to deal with this issue. IMHO, time working on that is better spent than time trying to prevent .pgpass files from working.
>
> afaik, the .pgpass file is something the user creates with his text editor. if it was encrypted or hashed, there would need to be a client side utility to create it.

Yes of course, something like ssh-keygen(1) for example.

Alban Hertroys

--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.

!DSPAM:737,4bc4402710411493216889!

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message John R Pierce 2010-04-13 10:00:42 Re: prevent connection using pgpass.conf
Previous Message Sergey Konoplev 2010-04-13 06:32:59 Re: Dynamic Catalog Views