Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Tue, 11 Nov 2014 21:34:36 +0000 (UTC)
From: "Chris Nauroth (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12754358.1415676576000.473208.1415741676496@Atlassian.JIRA>
In-Reply-To: <JIRA.12754358.1415676576000@Atlassian.JIRA>
References: <JIRA.12754358.1415676576000@Atlassian.JIRA>
 <JIRA.12754358.1415676576229@arcas>
Subject: [jira] [Updated] (HDFS-7389) Named user ACL cannot stop the user
 from accessing the FS entity.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/HDFS-7389?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Nauroth updated HDFS-7389:
--------------------------------
       Resolution: Fixed
    Fix Version/s: 2.7.0
           Status: Resolved  (was: Patch Available)

I have committed this to trunk and branch-2.  Chunjun, thank you for report=
ing the bug.  Vinay, thank you for providing the patch.

> Named user ACL cannot stop the user from accessing the FS entity.
> -----------------------------------------------------------------
>
>                 Key: HDFS-7389
>                 URL: https://issues.apache.org/jira/browse/HDFS-7389
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.5.1
>            Reporter: Chunjun Xiao
>            Assignee: Vinayakumar B
>             Fix For: 2.7.0
>
>         Attachments: HDFS-7389-001.patch, HDFS-7389-002.patch
>
>
> In http://hortonworks.com/blog/hdfs-acls-fine-grained-permissions-hdfs-fi=
les-hadoop/:
> {quote}
> It=E2=80=99s important to keep in mind the order of evaluation for ACL en=
tries when a user attempts to access a file system object:
> 1. If the user is the file owner, then the owner permission bits are enfo=
rced.
> 2. Else if the user has a named user ACL entry, then those permissions ar=
e enforced.
> 3. Else if the user is a member of the file=E2=80=99s group or any named =
group in an ACL entry, then the union of permissions for all matching entri=
es are enforced.  (The user may be a member of multiple groups.)
> 4. If none of the above were applicable, then the other permission bits a=
re enforced.
> {quote}
> Assume we have a user UserA from group GroupA, if we config a directory a=
s following ACL entries:
> group:GroupA:rwx
> user:UserA:---
> According to the design spec above, userA should have no access permissio=
n to the file object, while actually userA still has rwx access to the dir.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)