[
https://issues.apache.org/jira/browse/ZOOKEEPER-847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Han updated ZOOKEEPER-847:
----------------------------------
Fix Version/s: (was: 3.5.3)
3.5.4
> 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
> Fix For: 3.5.4, 3.6.0
>
> 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
(v6.3.15#6346)
