All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olga Kornievskaia <aglo@umich.edu>
To: Trond Myklebust <trondmy@hammerspace.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: acls+kerberos (limitation)
Date: Wed, 18 Dec 2019 14:31:52 -0500	[thread overview]
Message-ID: <CAN-5tyGXUhhZVkrBxTwGP-Y2FXoMdN9kYtc9r0wS8P8EQuxyoQ@mail.gmail.com> (raw)
In-Reply-To: <f4595e80487d9ace332e2ae69bc0c539a5c029bb.camel@hammerspace.com>

On Wed, Dec 18, 2019 at 2:05 PM Trond Myklebust <trondmy@hammerspace.com> wrote:
>
> On Wed, 2019-12-18 at 12:47 -0500, Olga Kornievskaia wrote:
> > Hi folks,
> >
> > Is this a well know but undocumented fact that you can't set large
> > amount of acls (over 4096bytes, ~90acls) while mounted using
> > krb5i/krb5p? That if you want to get/set large acls, it must be done
> > over auth_sys/krb5?
> >
>
> It's certainly not something that I was aware of. Do you see where that
> limitation is coming from?

I haven't figure it exactly but gss_unwrap_resp_integ() is failing in
if (mic_offset > rcv_buf->len). I'm just not sure who sets up the
buffer (or why  rvc_buf->len is (4280) larger than a page can a
page-limit might make sense to for me but it's not). So you think it
should have been working.

> --
> Trond Myklebust
> Linux NFS client maintainer, Hammerspace
> trond.myklebust@hammerspace.com
>
>

  reply	other threads:[~2019-12-18 19:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-18 17:47 acls+kerberos (limitation) Olga Kornievskaia
2019-12-18 19:05 ` Trond Myklebust
2019-12-18 19:31   ` Olga Kornievskaia [this message]
2019-12-18 19:34     ` Chuck Lever
2019-12-20 18:15       ` Olga Kornievskaia
2019-12-20 18:28         ` Chuck Lever
2019-12-20 20:04           ` Olga Kornievskaia
2019-12-20 20:11             ` Chuck Lever
2019-12-20 20:53               ` Olga Kornievskaia
2019-12-20 20:57                 ` Chuck Lever

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=CAN-5tyGXUhhZVkrBxTwGP-Y2FXoMdN9kYtc9r0wS8P8EQuxyoQ@mail.gmail.com \
    --to=aglo@umich.edu \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trondmy@hammerspace.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.