Re: pg16 && GSSAPI && Heimdal/Macos - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg16 && GSSAPI && Heimdal/Macos
Date
Msg-id 151051.1741472800@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg16 && GSSAPI && Heimdal/Macos  ("Todd M. Kover" <kovert@omniscient.com>)
List pgsql-hackers
"Todd M. Kover" <kovert@omniscient.com> writes:
> 2) some option that makes the code path for gss_store_cred_into optional
> (what would you want to call it?)

If we do this, I see no need to call it anything.  Just make configure
probe for whether the selected GSS library has gss_store_cred_into.

The other options you mention seem strictly worse from a documentation
and testing standpoint, and all of them open the question of exactly
how much we care to rely on Heimdal.  I take your point that if a
particular platform has an insecure version of Heimdal, it's their
problem not ours.  However, my recollection from the discussion a
couple years back is that different platforms offer significantly
different Heimdal releases, and making our code work with all of
those would be our problem.  (That consideration is why I'm so
allergic to the client-side-support-only proposal.  It is NOT okay
if we can't test it.)

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Clarification on Role Access Rights to Table Indexes
Next
From: Florents Tselai
Date:
Subject: Re: encode/decode support for base64url