From: | "Henry B(dot) Hotz" <hotz(at)jpl(dot)nasa(dot)gov> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Fwd: [PATCHES] Preliminary GSSAPI Patches |
Date: | 2007-05-01 00:53:08 |
Message-ID: | 87DDE7FB-CB97-40A3-B06D-920D0BF04357@jpl.nasa.gov |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Don't you want to maintain some interoperability between 8.2 client/
server and 8.3 server/client at least? If you put my patches in 8.3,
and they work as well as I hope, then "in time" could be as soon as
8.4, I suppose.
To answer the question more directly: I do not know of any platform
that supports the "native" Kerb5 API that doesn't also support GSSAPI
for the simple reason that a Kerberos-only version of GSSAPI has been
bundled with both the MIT and Heimdal distributions for as long as I
can remember.
On Apr 30, 2007, at 4:48 PM, Tom Lane wrote:
> "Henry B. Hotz" <hotz(at)jpl(dot)nasa(dot)gov> writes:
>> I tend to regard this as a comparable migration to the Kerb4 -> Kerb5
>> one. In time it should be a complete replacement. In time we will
>> be able to rip out the existing Kerb5 code.
>
> Why "in time" and not immediately? Are there platforms that don't
> support the GSSAPI interface? If so, how would we ever retire the
> old code?
>
> regards, tom lane
------------------------------------------------------------------------
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 | Tom Lane | 2007-05-01 00:56:13 | Re: Fwd: [PATCHES] Preliminary GSSAPI Patches |
Previous Message | Tom Lane | 2007-04-30 23:48:38 | Re: Fwd: [PATCHES] Preliminary GSSAPI Patches |