Mailing-List: contact dev-help@zookeeper.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@zookeeper.apache.org
Date: Tue, 21 Jun 2016 22:24:58 +0000 (UTC)
From: "Chris Nauroth (JIRA)" <jira@apache.org>
To: dev@zookeeper.apache.org
Message-ID: <JIRA.12471535.1281704490000.17648.1466547898522@Atlassian.JIRA>
In-Reply-To: <JIRA.12471535.1281704490000@Atlassian.JIRA>
References: <JIRA.12471535.1281704490000@Atlassian.JIRA> <JIRA.12471535.1281704490781@arcas>
Subject: [jira] [Updated] (ZOOKEEPER-847) Missing acl check in zookeeper
 create
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 21 Jun 2016 22:25:02 -0000


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

Chris Nauroth updated ZOOKEEPER-847:
------------------------------------
    Fix Version/s:     (was: 3.5.2)
                   3.5.3

> 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.6.0, 3.5.3
>
>         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.4#6332)