accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3557) No write ACL set on /accumulo/instances/...
Date Thu, 05 Feb 2015 17:58:35 GMT

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

Keith Turner commented on ACCUMULO-3557:
----------------------------------------

Not that I know of.

> No write ACL set on /accumulo/instances/...
> -------------------------------------------
>
>                 Key: ACCUMULO-3557
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3557
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: zookeeper
>            Reporter: Josh Elser
>            Priority: Critical
>             Fix For: 1.7.0
>
>
> It's common for users to have four "arguments" to make a connection to Accumulo: zookeeper
quorum string, instance name, username and password.
> The instance name is used to find the instanceID using {{/accumulo/instances/...}} in
ZooKeeper. It appears that anyone can write in the {{/accumulo/instances}} ZNode. This seems
suspect, because any unauthenticated user can alter the state of ZooKeeper and break users
connecting to Accumulo or force them to connect to a different Accumulo instance.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message