From: Chuck Lever <chuck.lever@oracle.com>
To: Steve Dickson <steved@redhat.com>,
Benjamin Coddington <bcodding@redhat.com>,
"Andrew J. Romero" <romero@fnal.gov>
Cc: linux-nfs@vger.kernel.org
Subject: Re: GSSPROXY ( for NFS with sec=krb5, krb5i , krb5p ) is development still active or is it being depreciated
Date: Sat, 15 Mar 2025 11:33:46 -0400 [thread overview]
Message-ID: <73d2d11e-2d3d-49e8-b8b0-b3387df459e7@oracle.com> (raw)
In-Reply-To: <9e7f3d6a-0989-4778-a2c0-ffafdebefa87@redhat.com>
On 3/15/25 11:17 AM, Steve Dickson wrote:
>
>
> On 3/14/25 8:18 AM, Benjamin Coddington wrote:
>> On 13 Mar 2025, at 7:30, Andrew J. Romero wrote:
>>
>>> Hi
>>>
>>> Alexander Bokovoy provided excellent answers to most of my questions on
>>> this topic See: Thread: gssproxy security, configuration and life-cycle
>>> questions on gss-proxy@lists.fedorahosted.org
>>>
>>> Remaining question:
>>>
>>> Prior to RHEL-9 , in the section of the gssd man page ( under the
>>> heading
>>> CONFIGURATION FILE ... ....options that can be set on the command
>>> line
>>> can also be controlled through .... values set in the [gssd] section of
>>> /etc/nfs.conf ) there was a configuration parameter "use-gss-proxy"
>>
>> I don't see any git history of gssd.man with use-gss-proxy, but the value
>> does appear in nfs.conf.man. It has not been removed there. It probably
>> should be added to gssd.man.
> +1
>
>>
>>> why was this parameter removed from the current man page, can it be
>>> re-added ? ( apparently the parameter is still functional ... if that's
>>> the case , it should not simply be removed from the documentation
>>> with no
>>> commentary )
>>
>> I'm not sure thats what happened. It looks like it wasn't ever in
>> gssd.man
>> to me. Maybe Steve D can clarify?
>
> My question is does the use-gss-proxy param need to be on
> by default... I agree that parameter needs to be documented in the
> gssd.man man page... which smayhew as sent a patch.
>
> Does use-gss-proxy=yes add more complexity that is needed?
>
> Personally I would like to turn it off.
AIUI it is always off on clients, but some NFSD configs utilize
gssproxy. Not sure how you would code that in /etc/nfs.conf ...?
--
Chuck Lever
next prev parent reply other threads:[~2025-03-15 15:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 23:29 GSSPROXY ( for NFS with sec=krb5, krb5i , krb5p ) is development still active or is it being depreciated Andrew J. Romero
2025-03-13 11:30 ` Andrew J. Romero
2025-03-14 12:18 ` Benjamin Coddington
2025-03-14 14:45 ` Scott Mayhew
2025-03-14 14:57 ` Andrew J. Romero
2025-03-14 14:57 ` [nfs-utils PATCH] gssd.man: add documentation for use-gss-proxy nfs.conf option Scott Mayhew
2025-03-15 15:17 ` GSSPROXY ( for NFS with sec=krb5, krb5i , krb5p ) is development still active or is it being depreciated Steve Dickson
2025-03-15 15:33 ` Chuck Lever [this message]
2025-03-17 13:22 ` [nfs-utils PATCH v2] gssd.man: add documentation for use-gss-proxy nfs.conf option Scott Mayhew
2025-03-24 20:29 ` Steve Dickson
2025-09-04 17:52 ` GSSPROXY ( for NFS with sec=krb5, krb5i , krb5p ) is development still active or is it being depreciated Charles Hedrick
2025-09-04 19:13 ` Andrew Romero
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=73d2d11e-2d3d-49e8-b8b0-b3387df459e7@oracle.com \
--to=chuck.lever@oracle.com \
--cc=bcodding@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=romero@fnal.gov \
--cc=steved@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox