Re: Future of krb5 authentication - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Future of krb5 authentication
Date
Msg-id 469E4050.10703@hagander.net
Whole thread Raw
In response to Re: Future of krb5 authentication  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Future of krb5 authentication  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
Tom Lane wrote:
> Magnus Hagander <magnus@hagander.net> writes:
>> On Wed, Jul 18, 2007 at 10:46:58AM -0400, Tom Lane wrote:
>>> This needs to be fixed.
> 
>> Non, GSSAPI and krb5 are *not* mutually exclusive.
> 
>> SSPI and GSSAPI are mutually exclusive.
> 
> Color me confused then.  What's the difference?

SSPI is a Windows-only implementation of the GSSAPI protocol, that has a
different API.

GSSAPI works on Unix and on Windows (but only with addon libraries, such
as MIT (unix or win) or Heimdal (unix only)).

The confusion probably comes from that GSSAPI is both a protocol
(supported by SSPI as well) and an API (not supported by SSPI).

Now, SSPI integrates with Active Directory, so it doesn't work if you
don't want to join your workstation to the Kerberos realm. Or as in
Stephens case, you want to be *both* on the Active Directory and in a
non-trusted Unix Kerberos realm.


But we're talking two different issues. Deprecating/removing krb5 is a
different thing from having GSSAPI and SSPI mutually exclusive or not.

//Magnus


pgsql-hackers by date:

Previous
From: Gregory Stark
Date:
Subject: Re: Future of krb5 authentication
Next
From: Stephen Frost
Date:
Subject: Re: Future of krb5 authentication