All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Mayhew <smayhew@redhat.com>
To: Benjamin Coddington <bcodding@redhat.com>
Cc: "Andrew J. Romero" <romero@fnal.gov>, Steved <steved@redhat.com>,
	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: Fri, 14 Mar 2025 10:45:38 -0400	[thread overview]
Message-ID: <Z9RBEmMDJ_3FtEDq@aion> (raw)
In-Reply-To: <E11151A2-D253-4F26-BB94-5CDA22FEF1B6@redhat.com>

On Fri, 14 Mar 2025, 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.

I also looked at the repos we use to build the RHEL packages, and I
don't see any evidence that we ever shipped a RHEL-only patch that would
have documented use-gss-proxy in gssd.man.

Andrew - can you provide a specific RHEL package version where you saw this
documented in gssd.man (on the off change I missed something)?

Either way, I agree this should be documented.

-Scott
> 
> > 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?
> 
> Ben
> 
> 


  reply	other threads:[~2025-03-14 14:45 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 [this message]
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
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=Z9RBEmMDJ_3FtEDq@aion \
    --to=smayhew@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.