Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Received-SPF: pass (athena.apache.org: domain of zshen@hortonworks.com
 designates 209.85.192.175 as permitted sender)
MIME-Version: 1.0
Date: Tue, 16 Sep 2014 01:19:20 -0700
Message-ID: 
 <CAJS6+b6E9VViXyQ-D7gXMXub10HTRxooc2sUXZQ-SML-cYR+Bg@mail.gmail.com>
Subject: [DISUCSS] Reasonable Hadoop ACL Defaults
From: Zhijie Shen <zshen@hortonworks.com>
To: security@hadoop.apache.org,
	"yarn-dev@hadoop.apache.org" <yarn-dev@hadoop.apache.org>,
	"common-dev@hadoop.apache.org" <common-dev@hadoop.apache.org>
Content-Type: text/plain; charset=UTF-8

Hi folks,

There're a bunch of ACLs configuration defaults, which are set to "*":

1. yarn.admin.acl in yarn-default.xml
2. yarn.scheduler.capacity.root.default.[acl_submit_applications|acl_administer_queue]
in capacity-scheduler.xml
3. security.*.protocol.acl in hadoop-policy.xml

When ACL (or server authorization) is enabled, the resources that are
supposed to be protected are still accessible. However, anybody can
still access them because the default configurations are "*",
accepting anybody. These defaults seem not to make much sense, but
only confuse users. Instead, the reasonable behavior should be that
when ACL is enabled, a user is going to be denied by default unless we
explicitly add him/her into the admin ACLs or the authorized
user/group list.

I have a patch to invert "*" to " "  to block all users by default.
Please let me how what you think about it, and how we should progress.

Thanks,
Zhijie

-- 
Zhijie Shen
Hortonworks Inc.
http://hortonworks.com/

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.