You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Wei-Chiu Chuang (Jira)" <ji...@apache.org> on 2024/11/06 23:22:00 UTC

[jira] [Commented] (HDDS-11656) KeyInfo has hundreds of ACLs

    [ https://issues.apache.org/jira/browse/HDDS-11656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17896109#comment-17896109 ] 

Wei-Chiu Chuang commented on HDDS-11656:
----------------------------------------

OMDirectoryCreateRequest(WithFSO) also

> KeyInfo has hundreds of ACLs
> ----------------------------
>
>                 Key: HDDS-11656
>                 URL: https://issues.apache.org/jira/browse/HDDS-11656
>             Project: Apache Ozone
>          Issue Type: Bug
>            Reporter: Wei-Chiu Chuang
>            Priority: Major
>
> Related to HDDS-11655.
> We found a cluster where files are created with hundreds of ACLs.
> Here's the culprit: https://github.com/apache/ozone/blob/master/hadoop-ozone/common/src/main/java/org/apache/hadoop/ozone/om/helpers/OzoneAclUtil.java#L66
> When creating a file, Ozone client supplies the ACL by composing the current user's group. The problem is, if Ranger is enabled, these ACLs does not take effect, but they get saved into KeyInfo regardless.
> Potential problems and proposed solutions.
> (1) OM does not limit the number of ACLs. That could potentially lead to some kind of DDoS attack. We should update OMKeyCreateRequest(WithFSO)/OMFileCreateRequest(WithFSO), OMKeyAclRequest and its subclasses to add guardrails.
> (2) If Ranger is enabled, prune the ACLs provided by the client from KeyInfo in OMKeyCreateRequest(WithFSO)/OMFileCreateRequest(WithFSO).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org