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! -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
