[
https://issues.apache.org/jira/browse/SOLR-16457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17688762#comment-17688762
]
Jan Høydahl commented on SOLR-16457:
------------------------------------
I tested with Solr's docker image
{code}
docker run --rm -ti -p 8983:8983 apache/solr-nightly:9.2.0-SNAPSHOT bash
solr@a870ffc164f7:/opt/solr-9.2.0-SNAPSHOT$
{code}
Unfortunately, even if
[Dockerfile's|https://github.com/apache/solr/blob/main/solr/docker/templates/Dockerfile.body.template#L78]
{{WORKDIR}} is {{/opt/solr}}, we end up with the expanded path when running
{{bin/solr}}, so this change really has no effect here. An alternative is of
course to hardcode {{/opt/solr}} in the policy file, since this will cover both
defaults of linux installer and docker image. Other ideas?
> solr.data.home should not be set to empty string in bin/solr
> ------------------------------------------------------------
>
> Key: SOLR-16457
> URL: https://issues.apache.org/jira/browse/SOLR-16457
> Project: Solr
> Issue Type: Bug
> Components: cli
> Affects Versions: 9.0, 9.1
> Reporter: Kevin Risden
> Assignee: Kevin Risden
> Priority: Major
> Fix For: main (10.0), 9.2
>
> Attachments: fix_security_symlinks-1.patch,
> fix_security_symlinks.patch
>
> Time Spent: 4h 20m
> Remaining Estimate: 0h
>
> solr.data.home should not be set to empty string in bin/solr since that
> causes the security.policy to be more wide open than it should.
> solr.cmd does NOT have the same issue since it explicitly checks the case of
> empty SOLR_DATA_HOME before adding it.
> https://github.com/apache/solr/blob/main/solr/bin/solr.cmd#L1342
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
