[
https://issues.apache.org/jira/browse/HADOOP-6566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833609#action_12833609
]
Devaraj Das commented on HADOOP-6566:
-------------------------------------
Steve, the code that you commented with is part of Hadoop already? Looks like
we can add some checks to this for the permissions aspect. Assuming that all
directories are supposed to be owned by the user who is running the daemon
process, this method can also check for ownership of the directories where the
owner should be the same as the process owner. I don't think we want to
complicate it more than that. Makes sense?
> Hadoop daemons should not start up if the ownership/permissions on the
> directories used at runtime are misconfigured
> --------------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-6566
> URL: https://issues.apache.org/jira/browse/HADOOP-6566
> Project: Hadoop Common
> Issue Type: New Feature
> Components: security
> Reporter: Devaraj Das
> Fix For: 0.22.0
>
>
> The Hadoop daemons (like datanode, namenode) should refuse to start up if the
> ownership/permissions on directories they use at runtime are misconfigured or
> they are not as expected. For example, the local directory where the
> filesystem image is stored should be owned by the user running the namenode
> process and should be only readable by that user. We can provide this feature
> in common and HDFS and MapReduce can use the same.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
