Re: Encryption of .pgpass

From: "Hiroshi Saito" <z-saito(at)guitar(dot)ocn(dot)ne(dot)jp>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-patches(at)postgresql(dot)org>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>
Subject: Re: Encryption of .pgpass
Date: 2006-05-09 16:29:18
Message-ID: 020e01c67385$b8606ed0$01324d80@hiroshi5jz7dqj
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>

> What is the point of this? It seems to be complicating life to little
> purpose (except storing passwords that will fail in non-MD5 password
> methods --- given that people are talking about replacing MD5, that
> doesn't seem like a good forward-looking idea).

Ahh, yes. It is "crypt" ,"ident" and "pam"...
I do not think that "passwd" should be used primarily.
Then, So, it is clear sufix of md5. It may be a narrower use.
However, I have simplified that it can use as a method of
hiding it. It is suggestion. Is it accepted by including "crypt"?

Thanks.

Regards,
Hiroshi Saito

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Martijn van Oosterhout 2006-05-09 17:33:19 Re: Have configure complain about unknown options
Previous Message Tom Lane 2006-05-09 15:55:06 Re: Encryption of .pgpass