You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shalin Shekhar Mangar (JIRA)" <ji...@apache.org> on 2014/09/02 23:09:22 UTC
[jira] [Commented] (SOLR-4580) Support for protecting content in ZK
[ https://issues.apache.org/jira/browse/SOLR-4580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14118751#comment-14118751 ]
Shalin Shekhar Mangar commented on SOLR-4580:
---------------------------------------------
This has broken the start scripts as well as the cloud-dev scripts. On starting solr using ./bin/solr -c, I see the following in the logs:
{quote}
2204 [main] ERROR org.apache.solr.servlet.SolrDispatchFilter – Could not start Solr. Check solr/home property and the logs
2224 [main] ERROR org.apache.solr.core.SolrCore – null:java.lang.StringIndexOutOfBoundsException: String index out of range: -1
at java.lang.String.substring(String.java:1954)
at org.apache.solr.core.ZkContainer.stripChroot(ZkContainer.java:199)
at org.apache.solr.core.ZkContainer.initZooKeeper(ZkContainer.java:104)
at org.apache.solr.core.ZkContainer.initZooKeeper(ZkContainer.java:64)
at org.apache.solr.core.CoreContainer.load(CoreContainer.java:222)
at org.apache.solr.servlet.SolrDispatchFilter.createCoreContainer(SolrDispatchFilter.java:190)
at org.apache.solr.servlet.SolrDispatchFilter.init(SolrDispatchFilter.java:137)
at org.eclipse.jetty.servlet.FilterHolder.doStart(FilterHolder.java:119)
{quote}
> Support for protecting content in ZK
> ------------------------------------
>
> Key: SOLR-4580
> URL: https://issues.apache.org/jira/browse/SOLR-4580
> Project: Solr
> Issue Type: New Feature
> Components: SolrCloud
> Affects Versions: 4.2
> Reporter: Per Steffensen
> Assignee: Mark Miller
> Labels: security, solr, zookeeper
> Fix For: 5.0, 4.11
>
> Attachments: SOLR-4580.patch, SOLR-4580.patch, SOLR-4580.patch, SOLR-4580_branch_4x_r1482255.patch
>
>
> We want to protect content in zookeeper.
> In order to run a CloudSolrServer in "client-space" you will have to open for access to zookeeper from client-space.
> If you do not trust persons or systems in client-space you want to protect zookeeper against evilness from client-space - e.g.
> * Changing configuration
> * Trying to mess up system by manipulating clusterstate
> * Add a delete-collection job to be carried out by the Overseer
> * etc
> Even if you do not open for zookeeper access to someone outside your "secure zone" you might want to protect zookeeper content from being manipulated by e.g.
> * Malware that found its way into secure zone
> * Other systems also using zookeeper
> * etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org