From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Tony Caduto <tony_caduto(at)amsoftwaredesign(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Password issue revisited |
Date: | 2007-02-20 19:15:17 |
Message-ID: | 45DB48C5.1000103@hagander.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-general |
Tom Lane wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
>> Tony Caduto wrote:
>>> What about having a wallet type system where the user can create a pass
>>> phrase to protect a generated key that would get
>>> loaded once per session. That is how KDE allows users to store passwords.
>
>> If we wanted to do that, we could use the Windows API that's available
>> to do this. The idea with the pgpass flie is to have it compatible with
>> the unix version.
>
> More to the point, that's far outside the scope of this project. Use a
> PAM auth module that you like, or Kerberos or whatever. I'm way past
> tired of "let's put yet another authentication technology in libpq" requests.
Just to make things clear, this wouldn't be about another auth method.
Windows has an API to store arbitrary passwords in a "secure way". At
least it does in XP+, not sure if it was in 2000.
Not saying it's a good idea, but it's not another auth tech for libpq.
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2007-02-20 19:28:31 | Re: Password issue revisited |
Previous Message | Tom Lane | 2007-02-20 19:13:46 | Re: Password issue revisited |
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2007-02-20 19:28:31 | Re: Password issue revisited |
Previous Message | Tom Lane | 2007-02-20 19:13:46 | Re: Password issue revisited |