2004-09-13 18:05:54 +00:00
|
|
|
<?php
|
|
|
|
require_once("docutil.php");
|
2005-03-02 07:15:15 +00:00
|
|
|
page_head("Access control for GUI RPC");
|
2004-09-13 18:05:54 +00:00
|
|
|
echo "
|
|
|
|
By default the core client accepts GUI RPC connections
|
|
|
|
only from programs on the same host.
|
2005-03-02 07:15:15 +00:00
|
|
|
|
|
|
|
<p>
|
|
|
|
<b>
|
|
|
|
NOTE: this means that any user on the same machine
|
|
|
|
can control the core client.
|
|
|
|
This is undesirable; we are planning to add
|
|
|
|
a password-based protection mechanism to GUI RPC.
|
|
|
|
</b>
|
|
|
|
|
|
|
|
<p>
|
|
|
|
You can allow remote hosts to control a core client in two ways:
|
2004-09-13 18:05:54 +00:00
|
|
|
<ul>
|
|
|
|
<li> If you run the client with the
|
|
|
|
-allow_remote_gui_rpc command line option,
|
|
|
|
it will accept connections from any host.
|
2005-03-02 07:15:15 +00:00
|
|
|
This is not recommended unless the host is behind a firewall
|
|
|
|
that blocks the GUI RPC port (1043).
|
2004-09-13 18:05:54 +00:00
|
|
|
<li>
|
|
|
|
You can create
|
|
|
|
a file remote_hosts.cfg in your BOINC directory containing
|
2005-03-02 07:15:15 +00:00
|
|
|
a list of allowed DNS host names or IP addresses (one per line).
|
2004-09-13 18:05:54 +00:00
|
|
|
Those hosts will be able to connect.
|
|
|
|
The remote_hosts.cfg file can have comment lines that start with either a #
|
|
|
|
or a ; character as well.
|
|
|
|
</ul>
|
|
|
|
";
|
|
|
|
|
|
|
|
page_tail();
|
|
|
|
?>
|