[
https://issues.apache.org/jira/browse/SOLR-13985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17009881#comment-17009881
]
Robert Muir edited comment on SOLR-13985 at 1/7/20 4:27 PM:
------------------------------------------------------------
{quote}
The issue is pretty clear. Solr only accepts connections on localhost, but puts
a public IP address in live_nodes, overseer messages, etc.
{quote}
This "self-advertisement" seems like not a great design, it will make things
difficult on users. How/what logic is picking such 192.168.1.194 IP today? :)
And I assume whatever default behavior is magically coming up with
"192.168.1.194" breaks currently all the time across different configurations
(e.g. reverse proxy in front), and the user must manually override with special
"publish" configuration?
It is good that you found the issue here, because we should be encouraging such
safe configurations which are probably difficult today (e.g. nodes talking to
each other over private network infra and not all exposed directly to the
internet).
Ideally this could be removed completely, and instead if nodeB talks to nodeA,
nodeA knows how to talk to nodeB by looking at the IP address that nodeB used,
"call be back on the phone number I called you on". It would give good default
behavior, and you wouldn't need to specify any "publish" stuff unless you were
doing something screwed-up (like exposing everything to the internet).
was (Author: rcmuir):
{quote}
The issue is pretty clear. Solr only accepts connections on localhost, but puts
a public IP address in live_nodes, overseer messages, etc.
{quote}
This "self-advertisement" seems like not a great design, it will make things
difficult on users. How/what logic is picking such 192.168.1.194 IP today? :)
And I assume whatever default behavior is magically coming up with
"192.168.1.194" breaks currently all the time across different configurations
(e.g. reverse proxy in front), and the user must manually override with special
"publish" configuration?
It is good that you found the issue here, because we should be encouraging such
safe configurations which are probably difficult today (e.g. nodes talking to
each other over private network infra and not all exposed directly to the
internet).
Ideally this could be removed completely, and instead if nodeB talks to nodeA,
nodeA knows how to talk to nodeB by looking at the IP address that nodeA used.
It would give good default behavior, and you wouldn't need to specify any
"publish" stuff unless you were doing something screwed-up (like exposing
everything to the internet).
> bind to localhost by default
> ----------------------------
>
> Key: SOLR-13985
> URL: https://issues.apache.org/jira/browse/SOLR-13985
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Robert Muir
> Assignee: Jason Gerlowski
> Priority: Major
> Fix For: master (9.0)
>
> Attachments: SOLR-13985.patch, SOLR-13985.patch, SOLR-13985.patch,
> SOLR-13985.patch
>
>
> Currently solr binds to all interfaces by default.
> The default should be safer, so that e.g. the user is not exposed to the
> internet until they make an explicit step to do so.
--
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
