[
https://issues.apache.org/jira/browse/HADOOP-10758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16099863#comment-16099863
]
Lars Francke commented on HADOOP-10758:
---------------------------------------
I know this issue is old but I'm wondering:
The user can specify the ACL to check against using the key.acl.name property.
That seems a bit insecure to me, no? If I want to make sure that a key with the
name "foo" can only be managed by certain users then I have a hard time to
enforce that when it is being created with a different key.acl.name. Am I
missing something? Is this by design?
The fact that the whole attributes field and key.acl.name thing is not
documented doesn't help.
> KMS: add ACLs on per key basis.
> -------------------------------
>
> Key: HADOOP-10758
> URL: https://issues.apache.org/jira/browse/HADOOP-10758
> Project: Hadoop Common
> Issue Type: Improvement
> Components: security
> Affects Versions: 3.0.0-alpha1
> Reporter: Alejandro Abdelnur
> Assignee: Arun Suresh
> Fix For: 2.6.0
>
> Attachments: HADOOP-10758.1.patch, HADOOP-10758.2.patch,
> HADOOP-10758.3.patch, HADOOP-10758.4.patch, HADOOP-10758.5.patch,
> HADOOP-10758.6.patch, HADOOP-10758.7.patch, HADOOP-10758.8.patch,
> HADOOP-10758.9.patch
>
>
> The KMS server should enforce ACLs on per key basis.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
