From: "Goetz, Patrick G" <pgoetz@math.utexas.edu>
To: Daniel Kobras <kobras@puzzle-itc.de>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: Does NFSv4 translate POSIX ACL's?
Date: Thu, 22 Aug 2019 22:02:14 +0000 [thread overview]
Message-ID: <3db56f4d-9e7c-bb67-4de4-e723e20a9cb7@math.utexas.edu> (raw)
In-Reply-To: <224D3569-14EA-4533-A5DC-CD4903EF4772@puzzle-itc.de>
Hi Daniel -
Thanks so much for your help! That was indeed the problem. I didn't
realize that default ACL's don't count as actionable ACL's (other than
to dictate authorization for new sub-directories and files).
On 8/20/19 2:14 PM, Daniel Kobras wrote:
> Hi!
>
>> Am 20.08.2019 um 20:35 schrieb Goetz, Patrick G <pgoetz@math.utexas.edu>:
>>
>> I have an NFSv4 exported folder (base filesystem: XFS) which must afford
>> read access to a program on folders which are otherwise hidden from the
>> public. On the NFS server:
>>
>> root@kraken:/EM/EMtifs# getfacl pgoetz
>> # file: pgoetz
>> # owner: pgoetz
>> # group: cns-cnsitlabusers
>> user::rwx
>> group::r-x
>> other::---
>> default:user::rwx
>> default:user:cryosparc_user:r-x
>> default:group::r-x
>> default:mask::r-x
>> default:other::---
>
> There’s only a default ACL (which is inherited to new objects), but no proper ACL on the directory itself. Have you tried
>
> setfacl -m u:cryosparc_user:rx
>
> already?
>
> Kind regards,
>
> Daniel
>
next prev parent reply other threads:[~2019-08-22 22:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 18:35 Does NFSv4 translate POSIX ACL's? Goetz, Patrick G
2019-08-20 19:14 ` Daniel Kobras
2019-08-22 22:02 ` Goetz, Patrick G [this message]
2019-08-20 19:15 ` J. Bruce Fields
2019-08-22 22:03 ` Goetz, Patrick G
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=3db56f4d-9e7c-bb67-4de4-e723e20a9cb7@math.utexas.edu \
--to=pgoetz@math.utexas.edu \
--cc=kobras@puzzle-itc.de \
--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