GitHub user Randgalt opened a pull request: https://github.com/apache/zookeeper/pull/248
[ZOOKEEPER-2779} Provide a means to disable setting of the Read Only ACL for the reconfig node Provide a means to disable setting of the Read Only ACL for the reconfig node added in ZOOKEEPER-2014. That change made it very cumbersome to use the reconfig feature and also could worsen security as the entire ZK database is open to "super" user while the reconfig node is being changed (the only possible method as of ZOOKEEPER-2014). You can merge this pull request into a Git repository by running: $ git pull https://github.com/Randgalt/zookeeper ZOOKEEPER-2779 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/zookeeper/pull/248.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #248 ---- commit de07e525ec8b4aa24283eedb159f8df2b576e71b Author: randgalt <jor...@jordanzimmerman.com> Date: 2017-05-09T14:12:41Z Provide a means to disable setting of the Read Only ACL for the reconfig node added in ZOOKEEPER-2014. That change made it very cumbersome to use the reconfig feature and also could worsen security as the entire ZK database is open to "super" user while the reconfig node is being changed (the only possible method as of ZOOKEEPER-2014). ---- --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---