| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, Dave Page <dpage(at)postgresql(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Future of krb5 authentication |
| Date: | 2007-07-18 21:52:03 |
| Message-ID: | 10614.1184795523@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:
> The issue is *not* about GSSAPI vs krb5. It's with GSSAPI vs SSPI.
> The wire protocol is the same for them. It's a matter of which *client
> library* should be used to produce the packets that go over the network.
Oh, they're fully interchangeable at the wire level? Is this true both
with respect to the PG client/backend protocol and the protocol to the
authentication server? If there's no interoperability issues then I
agree that a configure-time choice is sufficient for selecting which
library to use.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-07-18 21:54:51 | Re: Why so many out-of-disk-space failures on buildfarm machines? |
| Previous Message | Gregory Stark | 2007-07-18 21:49:18 | Re: Future of krb5 authentication |