From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Konstantin Izmailov <kizmailov(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: question about SSIS |
Date: | 2009-05-22 19:24:55 |
Message-ID: | 29175.1243020295@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> In his scenario, different clients connecting from the same subnet (so
> they can't use different pg_hba lines) need to use different
> authentication methods. (IIRC, this is an environment coming from
> Microsoft SQL Server which does support this)
Perhaps he could use the user name or database name to distinguish
them in pg_hba.conf?
> I think what he's asking for is the ability for a line in the server to
> allow multiple authentication methods, and then for the client to be
> able to specify which one of these it uses.
There's no way we could implement that without a protocol change,
and it doesn't seem worth it to me. The idea that the client gets
to choose seems like a bad idea from a security standpoint anyhow...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Watson | 2009-05-22 19:41:19 | duplicate rows in query |
Previous Message | Tom Lane | 2009-05-22 19:20:26 | Re: How to update stavaluesN columns in pg_statistics (type anyarry) |