From: | "Henry B(dot) Hotz" <hotz(at)jpl(dot)nasa(dot)gov> |
---|---|
To: | Kris Jurka <books(at)ejurka(dot)com> |
Cc: | Peter Koczan <pjkoczan(at)gmail(dot)com>, pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: JDBC and GSSAPI/Krb5 |
Date: | 2007-12-07 07:26:45 |
Message-ID: | E1E5362E-41F5-45AC-B33D-75B946324766@jpl.nasa.gov |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Dec 6, 2007, at 12:05 PM, Kris Jurka wrote:
>
>
> On Thu, 6 Dec 2007, Henry B. Hotz wrote:
>
>> If they are wire-compatible then there is no reason to use a
>> different value on the wire to differentiate them. This is the
>> point that I said I didn't understand.
>>
>
> I think the point is that a client using the SSPI library can
> operate wire-compatibly with a server using the GSSSPI library, but
> that only happens with the auth type of "gss". When the "sspi"
> auth type is used, that signals to a client using the SSPI library
> to do something non wire-compatible and that's why the two auth
> types are used.
>
> Kris Jurka
I'm not enough of a Windows person to know if that makes sense. I'll
ask Magnus when I get far enough it matters. I think my choices are
to ignore the difference or to only support the two GSS types.
------------------------------------------------------------------------
The opinions expressed in this message are mine,
not those of Caltech, JPL, NASA, or the US Government.
Henry(dot)B(dot)Hotz(at)jpl(dot)nasa(dot)gov, or hbhotz(at)oxy(dot)edu
From | Date | Subject | |
---|---|---|---|
Next Message | sulfinu | 2007-12-07 12:48:21 | JDBC driver patch for non-ASCII users |
Previous Message | Kris Jurka | 2007-12-06 20:05:52 | Re: JDBC and GSSAPI/Krb5 |