linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Ben H <bhendin@gmail.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Fwd: question re: NO_AUTH_DATA_REQUIRED
Date: Tue, 12 Aug 2014 14:19:41 -0400	[thread overview]
Message-ID: <20140812181941.GA25197@fieldses.org> (raw)
In-Reply-To: <CAAd7auZOmk4_tR0WnqFCbv3CSLF=BXoQjtdsQZaB0dgoOYNREw@mail.gmail.com>

On Mon, Aug 11, 2014 at 01:23:38PM -0500, Ben H wrote:
> First off, apologies if this is not the correct list.
> I saw questions like this on the old nfsv4@linux-nfs.org list, and
> believe that this replaces that.
> Please direct me to a more appropriate resource if available.
> If I'm in the right place, I'm looking for some schooling...
> 
> I have been working with NFSv4 sec=krb5 and early on ran into the PAC
> issue described nebulously throughout various resources on the web.
> 
> When working with AD users who are in multiple groups (in my
> experiments, seems to be approximately 20) I have to set
> NO_AUTH_DATA_REQUIRED on the userAccountControl of my NFS server
> principal so that the PAC is not sent and the TGS-REQ can occur over
> UDP.
> 
> What I cannot find an answer for is why/where exactly is this
> limitation introduced?
> Kerberos can deal with the larger packets via TCP, and some Kerberos
> implementation may enforce TCP even on smaller packets.

The main problem is the kernel<->rpc.svcgssd interface.

The problem should be fixed on newer distros that use gss-proxy.

--b.

      reply	other threads:[~2014-08-12 18:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAAd7aua8+U=eFZUFhjp8gcnYv9BkvjOgSbLJbGp_Qg9O5cHH5w@mail.gmail.com>
2014-08-11 18:23 ` Fwd: question re: NO_AUTH_DATA_REQUIRED Ben H
2014-08-12 18:19   ` 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=20140812181941.GA25197@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=bhendin@gmail.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).