[
https://issues.apache.org/jira/browse/ZOOKEEPER-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14607496#comment-14607496
]
Rakesh R commented on ZOOKEEPER-2221:
-------------------------------------
Good catch [~cnauroth]. Yes, I agree with you, we need to update only
{{src/docs/src/documentation/content/xdocs/zookeeperAdmin.xml}} file so that it
will get reflected in the guide after rebuild. It is not required to update the
{{.html}} and {{.pdf}} files. I'm not really sure the reason of maintaining
these files in the source repository.
> Zookeeper JettyAdminServer server should start on configured IP.
> ----------------------------------------------------------------
>
> Key: ZOOKEEPER-2221
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2221
> Project: ZooKeeper
> Issue Type: Bug
> Components: quorum
> Affects Versions: 3.5.0
> Reporter: Surendra Singh Lilhore
> Assignee: Surendra Singh Lilhore
> Attachments: ZOOKEEPER-2221.patch, ZOOKEEPER-2221.patch,
> ZOOKEEPER-2221_1.patch
>
>
> Currently JettyAdminServer starting on "0.0.0.0" IP. "0.0.0.0" means "all IP
> addresses on the local machine". So, if your webserver machine has two ip
> addresses, 192.168.1.1(private) and 10.1.2.1(public), and you allow a
> webserver daemon like apache to listen on 0.0.0.0, it will be reachable at
> both of those IPs.
> This is security issue. webserver should be accessible from only configured IP
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
