From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Lars Kanis <kanis(at)comcard(dot)de>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCH] user mapping extension to pg_ident.conf |
Date: | 2009-07-22 12:53:47 |
Message-ID: | 18190.1248267227@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
>> Yup, you would need a protocol change that would allow the client to
>> change its mind about what the username was after it got the auth
>> challenge. And then what effects does that have on username-sensitive
>> pg_hba.conf decisions? We go back and change our minds about the
>> challenge type, perhaps? The whole thing seems like a nonstarter to me.
> "challenge type"? Not sure I understand what you are referring to here.
The point is that pg_hba.conf allows the selection of auth method to
depend on username. What happens if, after being told auth method is
(say) Kerberos, the client comes back and wants to use a different
username that should have resulted in a different auth method according
to pg_hba.conf? It's not hard to construct scenarios where that would
be seen as a security breach.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2009-07-22 12:57:55 | Re: [PATCH] user mapping extension to pg_ident.conf |
Previous Message | Andrew Dunstan | 2009-07-22 12:48:42 | Re: Upgrading our minimum required flex version for 8.5 |