[
https://issues.apache.org/jira/browse/SOLR-16457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17689241#comment-17689241
]
Kevin Risden commented on SOLR-16457:
-------------------------------------
{code:java}
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?
{code}
I'm having a hard time following what you are trying to test in Docker now. If
we only have to fix Docker then you can do something like
https://github.com/apache/solr/commit/a46d75ac8dd#diff-97623550d4ca71f93eed3e3abd23877b1a3f87555ecdee0cd71310d44f4d648d
or something else in the Dockerfile.
> 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]
