From: Simo Sorce <simo@redhat.com>
To: Olga Kornievskaia <aglo@umich.edu>, Chuck Lever <chuck.lever@oracle.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH RFC 0/4] Use correct NFSv4.0 callback credential
Date: Fri, 18 May 2018 16:42:38 -0400 [thread overview]
Message-ID: <1526676158.10011.29.camel@redhat.com> (raw)
In-Reply-To: <CAN-5tyGOK+5OUGrn5i=97y+OhanNa8jdnof4BCXvFpW0-ch9dQ@mail.gmail.com>
On Fri, 2018-05-18 at 16:19 -0400, Olga Kornievskaia wrote:
> I think the srchost is needed only if we are going to deal with doing
> something cross-DNS domains so say if
> host@klim.ib.1015granger.net will authenticate to
> nfs@klim.roce.1015granger.net, then the target's domain would not be
> sufficient to match which source domain name to use. So if this the
> use case, then sorry I just had to think out-loud to get here, then we
> do need srcdomain (and it's really a domain isn't it and not host
> that's of interest?).
I am confused about your use of the term "domain" here.
Can you use either REALM or hostname appropriately ?
Or are you using the term "domain" to mean FQDN ?
Simo.
--
Simo Sorce
Sr. Principal Software Engineer
Red Hat, Inc
next prev parent reply other threads:[~2018-05-18 20:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 15:39 [PATCH RFC 0/4] Use correct NFSv4.0 callback credential Chuck Lever
2018-05-18 15:39 ` [PATCH RFC 1/4] sunrpc: Enable the kernel to specify the hostname part of service principals Chuck Lever
2018-05-18 15:39 ` [PATCH RFC 2/4] sunrpc: Extract target name into svc_cred Chuck Lever
2018-05-18 15:39 ` [PATCH RFC 3/4] nfsd: Use correct credential for NFSv4.0 callback with GSS Chuck Lever
2018-05-18 15:39 ` [PATCH RFC 4/4] nfsd: Remove callback_cred Chuck Lever
2018-05-18 16:03 ` [PATCH RFC 0/4] Use correct NFSv4.0 callback credential Simo Sorce
2018-05-18 16:53 ` Chuck Lever
2018-05-18 17:07 ` Simo Sorce
2018-05-29 18:21 ` Fwd: " Chuck Lever
2018-05-29 19:13 ` J. Bruce Fields
2018-05-29 19:14 ` Chuck Lever
2018-08-15 22:27 ` Chuck Lever
2018-08-16 13:19 ` J. Bruce Fields
2018-05-18 18:53 ` Olga Kornievskaia
2018-05-18 19:05 ` Simo Sorce
2018-05-18 20:02 ` Olga Kornievskaia
2018-05-18 19:23 ` Chuck Lever
2018-05-18 20:11 ` Olga Kornievskaia
2018-05-18 20:19 ` Olga Kornievskaia
2018-05-18 20:42 ` Simo Sorce [this message]
2018-05-18 20:39 ` Simo Sorce
2018-05-18 20:56 ` Chuck Lever
2018-05-18 21:02 ` Olga Kornievskaia
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=1526676158.10011.29.camel@redhat.com \
--to=simo@redhat.com \
--cc=aglo@umich.edu \
--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).