hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-6962) FileSystem.mkdirs(Path, FSPermission) should use the permission for all of the created directories
Date Thu, 03 Jan 2013 01:22:13 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-6962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Allen Wittenauer updated HADOOP-6962:
-------------------------------------

         Priority: Blocker  (was: Critical)
    Fix Version/s: 1.2.0

I'm changing this to a blocker for 1.2.0.  This is a pretty major security hole, when one
considers that HDFS does permission inheritance. 

The only real choices appear to be:
a) Use 0777 + applied umask (i.e., POSIX)
b) Use inherited perms + applied umask (what I remember from the testing we did in Hadoop
0.14/15-ish)

I don't view this as a backwards compatibility problem as much as I view this as a regression.
 I'm fairly confident that at some point in time this was working as intended (option b),
but somewhere along the way no one noticed that it was broken.
                
> FileSystem.mkdirs(Path, FSPermission) should use the permission for all of the created
directories
> --------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-6962
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6962
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs, security
>    Affects Versions: 1.0.4
>            Reporter: Owen O'Malley
>            Assignee: Daryn Sharp
>            Priority: Blocker
>              Labels: security
>             Fix For: 1.2.0
>
>         Attachments: HADOOP-6962.patch
>
>
> Currently, FileSystem.mkdirs only applies the permissions to the last level if it was
created. It should be applied to *all* levels that are created.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message