zookeeper-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Enrico Olivelli (Jira)" <j...@apache.org>
Subject [jira] [Updated] (ZOOKEEPER-847) Missing acl check in zookeeper create
Date Fri, 06 Sep 2019 15:44:02 GMT

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Enrico Olivelli updated ZOOKEEPER-847:
--------------------------------------
    Fix Version/s: 3.5.7

> Missing acl check in zookeeper create
> -------------------------------------
>
>                 Key: ZOOKEEPER-847
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-847
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: java client
>    Affects Versions: 3.3.1, 3.3.2, 3.3.3
>            Reporter: Patrick Datko
>            Priority: Major
>             Fix For: 3.6.0, 3.5.6, 3.5.7
>
>         Attachments: ZOOKEEPER-847.patch
>
>
> I watched the source of the zookeeper class and I missed an acl check in the asynchronous
version of the create operation. Is there any reason, that in the asynch version is no
> check whether the acl is valid, or did someone forget to implement it. It's interesting
because we worked on a refactoring of the zookeeper client and don't want to implement a bug.
> The following code is missing:
>         if (acl != null && acl.size() == 0) {
>             throw new KeeperException.InvalidACLException();
>         }



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Mime
View raw message