[
https://issues.apache.org/jira/browse/HADOOP-12102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14602162#comment-14602162
]
Kai Sasaki commented on HADOOP-12102:
-------------------------------------
[~cnauroth] Thank you so much for comment!
I think we should care about the backwards-compatibility with the maximum
priority. If we must keep the protocol layer as it is now, we can implement
this ACL in HDFS component not Common component.
Or if we can change the protocol layer when upgrading to 3.0.0, it might be
also option.
Implementing host/IP based ACL outside of service-level ACL can also be
possible, but it may bring the complexity and overlap of codebase.
> Add option to list up allowed hosts that can do any operation as generic ACL.
> -----------------------------------------------------------------------------
>
> Key: HADOOP-12102
> URL: https://issues.apache.org/jira/browse/HADOOP-12102
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 2.7.0
> Reporter: Kai Sasaki
> Assignee: Kai Sasaki
> Priority: Minor
>
> Current NameNode receives all operations through client protocol from any
> hosts.
> However, some critical operations such as format should be restricted with
> not only Kerberos authentication but also with host names in order to prevent
> us from formatting NameNode by mistake. It is better to add option to write
> some allowed hosts which can do any operations to NameNode.
> Although originally this is about HDFS daemons, this feature should be
> implemented as one of generic ACL.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
