From: Kevin Coffman <kwc@citi.umich.edu>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/2] Give svcgssd access to kernel's supported enctypes
Date: Thu, 3 Mar 2011 09:28:18 -0500 [thread overview]
Message-ID: <AANLkTikhZV1ybQ0F4Yt9SQLvt8xRyuGZA0fBNPyu3sb-@mail.gmail.com> (raw)
In-Reply-To: <20110303062621.GG7724@fieldses.org>
On Thu, Mar 3, 2011 at 1:26 AM, J. Bruce Fields <bfields@fieldses.org> wrote:
> On Wed, Mar 02, 2011 at 07:51:40PM -0500, Kevin Coffman wrote:
>> Make the kernel's supported enctypes available to user-land
>> (svcgssd) via a new proc file. The client side already gets
>> this information in the upcall to gssd, we need to make it
>> available to svcgssd.
>
> They look good to me; I'll queue them up for 2.6.39 if nobody else sees
> a problem.
>
> Do you have the nfs-utils bits ready as well?
>
> --b.
I do, but I wanted to try and add something to detect whether the
Kerberos code has been updated to honor the request to limit the
encryption types (in the accept_sec_context path), and give a helpful
warning message. However, that may turn out to be more work than it
is worth. I will be sending patches soon.
K.C.
prev parent reply other threads:[~2011-03-03 14:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 0:51 [PATCH 0/2] Give svcgssd access to kernel's supported enctypes Kevin Coffman
2011-03-03 0:51 ` [PATCH 1/2] gss:krb5 only include enctype numbers in gm_upcall_enctypes Kevin Coffman
2011-03-03 0:51 ` [PATCH 2/2] nfsd: add proc file listing kernel's gss_krb5 enctypes Kevin Coffman
2011-03-03 6:26 ` [PATCH 0/2] Give svcgssd access to kernel's supported enctypes J. Bruce Fields
2011-03-03 14:28 ` Kevin Coffman [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=AANLkTikhZV1ybQ0F4Yt9SQLvt8xRyuGZA0fBNPyu3sb-@mail.gmail.com \
--to=kwc@citi.umich.edu \
--cc=bfields@fieldses.org \
--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).