[
https://issues.apache.org/jira/browse/SOLR-13972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17176242#comment-17176242
]
Jason Gerlowski commented on SOLR-13972:
----------------------------------------
Oh, ok. If that's what we typically do. I think it's confusing either way.
The way I look at this bug, it means that the goal of this Jira was never
achieved in the first place. 8.4 never had correct error messages here, so why
bother preserving the 8.4 fix version here. (i.e. Unless someone digs into the
comments here, they'll see that this was working in 8.4 when it wasn't).
But I understand the concern about the CHANGES.txt numbers. I'll open a new
jira.
> Insecure Solr should generate startup warning
> ---------------------------------------------
>
> Key: SOLR-13972
> URL: https://issues.apache.org/jira/browse/SOLR-13972
> Project: Solr
> Issue Type: Bug
> Reporter: Ishan Chattopadhyaya
> Assignee: Jason Gerlowski
> Priority: Critical
> Fix For: master (9.0), 8.4
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> Warning to the effect of, start Solr with: "solr auth enable -credentials
> solr:foo -blockUnknown true” (or some other way to achieve the same effect)
> if you want to expose this Solr instance directly to users. Maybe the link to
> the ref guide discussing all this might be in good measure here.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
