[
https://issues.apache.org/jira/browse/HADOOP-10758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16100668#comment-16100668
]
Lars Francke commented on HADOOP-10758:
---------------------------------------
I've read the docs and the code but the docs don't mention {{key.acl.name}} at
all.
Yes it's used for creates only, but imagine someone has the MANAGEMENT ACLs for
key {{foo}}. He can now create _any_ key by just setting {{key.acl.name}} to
{{foo}} for this newly created key. The default ACLs don't even come into play.
And that is because the method {{authorizeCreateKey}} in blindly takes the ACL
to use from the user input. That, in my opinion, is not a good idea.
> 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]
