linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Scott Mayhew <smayhew@redhat.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: chuck.lever@oracle.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH RFC 0/2] nfsd: add principal to the data being tracked by nfsdcld
Date: Wed, 31 Jul 2019 08:11:33 -0400	[thread overview]
Message-ID: <20190731121133.GQ4131@coeurl.usersys.redhat.com> (raw)
In-Reply-To: <20190730215654.GC3544@fieldses.org>

On Tue, 30 Jul 2019, J. Bruce Fields wrote:

> On Tue, Jul 30, 2019 at 05:54:28PM -0400, J. Bruce Fields wrote:
> > How does it fail when principals are longer?  Does it error out, or
> > treat two principals as equal if they agree in the first 1024 bytes?
> 
> I guess it's being compared against a string passed from gss-proxy?  We
> could also check for limits there.

I'm using cr_principal (servicetype@hostname) since it's set by both
gssproxy and rpc.svcgssd.  cr_raw_principal (servicetype/hostname@REALM)
is only set by gssproxy.

-Scott
> 
> --b.

  reply	other threads:[~2019-07-31 12:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-30 21:08 [PATCH RFC 0/2] nfsd: add principal to the data being tracked by nfsdcld Scott Mayhew
2019-07-30 21:08 ` [PATCH RFC 1/2] nfsd: add a "GetVersion" upcall for nfsdcld Scott Mayhew
2019-07-30 21:08 ` [PATCH RFC 2/2] nfsd: add support for upcall version 2 Scott Mayhew
2019-07-30 21:54 ` [PATCH RFC 0/2] nfsd: add principal to the data being tracked by nfsdcld J. Bruce Fields
2019-07-30 21:56   ` J. Bruce Fields
2019-07-31 12:11     ` Scott Mayhew [this message]
2019-07-31 12:07   ` Scott Mayhew
2019-07-31 14:31     ` J. Bruce Fields

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=20190731121133.GQ4131@coeurl.usersys.redhat.com \
    --to=smayhew@redhat.com \
    --cc=bfields@fieldses.org \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).