Re: Naming of gss_accept_deleg - Mailing list pgsql-hackers

From Abhijit Menon-Sen
Subject Re: Naming of gss_accept_deleg
Date
Msg-id ZGd7F5ycNYiOXeuo@toroid.org
Whole thread Raw
In response to Re: Naming of gss_accept_deleg  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Naming of gss_accept_deleg
List pgsql-hackers
At 2023-05-19 09:16:09 -0400, bruce@momjian.us wrote:
>
> On Fri, May 19, 2023 at 09:07:26AM -0400, Stephen Frost wrote:
> > 
> > > Why is the new PG 16 GUC called "gss_accept_deleg" and not
> > > "gss_accept_delegation"?  The abbreviation here seems atypical.
> > 
> > At the time it felt natural to me but I don't feel strongly about it,
> > happy to change it if folks would prefer it spelled out.
> 
> Yes, please do spell it out, thanks.  The fact "deleg" looks similar to
> "debug" also doesn't help.

Note that GSS-API itself calls it the "DELEG" flag:

    if (conn->gcred != GSS_C_NO_CREDENTIAL)
            gss_flags |= GSS_C_DELEG_FLAG;

I would also prefer a GUC named gss_accept_delegation, but the current
name matches the libpq gssdeleg connection parameter and the PGSSDELEG
environment variable. Maybe there's something to be said for keeping
those three things alike?

-- Abhijit



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Naming of gss_accept_deleg
Next
From: Tom Lane
Date:
Subject: Re: Naming of gss_accept_deleg