From: "J. Bruce Fields" <bfields@fieldses.org>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: William Andros Adamson <andros@netapp.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 1/1] SUNRPC add rpc_gss_svc_t to gssd upcall
Date: Fri, 12 Dec 2014 22:45:19 -0500 [thread overview]
Message-ID: <20141213034518.GA28337@fieldses.org> (raw)
In-Reply-To: <CAHQdGtQkrjWV61qPCN=vbo9zy1CKxu0Fp00vvpWV57tWWJ9FhA@mail.gmail.com>
On Fri, Dec 12, 2014 at 07:26:39PM -0500, Trond Myklebust wrote:
> Hi Andy
>
> On Fri, Dec 12, 2014 at 5:33 PM, <andros@netapp.com> wrote:
> > From: Andy Adamson <andros@netapp.com>
> >
> > Otherwise rpc.gssd will send a V4 NULL RPCSEC_GSS_INIT call with an RPCSEC_GSS
> > service of rpc_gss_svc_none for rpc_sec_gss_svc_integrity/privacy requests
> > from the kernel.
>
> I thought this behaviour of using rpc_gss_svc_none for the RPCSEC_GSS
> negotiation in userland and then "stepping up" to a stricter service
> in the kernel had been declared legal by the powers that be.
Yes, in fact:
https://www.ietf.org/rfc/rfc2203.txt 5.2.2:
In a creation request, the seq_num and service fields are
undefined and both must be ignored by the server.
--b.
prev parent reply other threads:[~2014-12-13 3:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 22:33 [PATCH 1/1] SUNRPC add rpc_gss_svc_t to gssd upcall andros
2014-12-13 0:26 ` Trond Myklebust
2014-12-13 3:45 ` J. Bruce Fields [this message]
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=20141213034518.GA28337@fieldses.org \
--to=bfields@fieldses.org \
--cc=andros@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.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