| | 1 | = Controlling BOINC remotely = |
| | 2 | |
| | 3 | |
| | 4 | == Remote control of the BOINC client == |
| | 5 | The BOINC core client typically is controlled by the [ManagerAdvanced BOINC Manager] running on the same machine: |
| | 6 | |
| | 7 | [[Image(http://boinc.berkeley.edu/gui_auth.png)]] The two programs communicate over a local connection, using 'GUI RPC' (Graphical User Interface Remote Procedure Call). It's also possible to use the BOINC Manager to control a core client on a different host: |
| | 8 | |
| | 9 | [[Image(http://boinc.berkeley.edu/gui_auth2.png)]] You can use [http://boinc.berkeley.edu/addons.php add-on programs] such as BOINCView to control many BOINC clients at once: [[Image(http://boinc.berkeley.edu/gui_auth3.png)]] |
| | 10 | == Access control for GUI RPC == |
| | 11 | Since GUI RPCs can control the BOINC client (e.g. attaching/detaching projects) it is important to protect your BOINC client from unauthorized control. There are two levels of protection: |
| | 12 | |
| | 13 | |
| | 14 | * GUI RPCs are authenticated with a '''GUI RPC password'''. This is stored with the client in the file '''gui_rpc_auth.cfg'''. When BOINC first runs, it generates a long, random password. You can change it if you like. |
| | 15 | * You can specify a set of hosts from which RPCs are allowed. By default, RPCs are allowed only from the same host. |
| | 16 | |
| | 17 | A GUI RPC is handled only if it passes both levels of protection. |
| | 18 | == Allowing RPCs from remote hosts == |
| | 19 | By default the core client accepts GUI RPCs only from the same host. You can allow remote hosts to control a core client in two ways: |
| | 20 | |
| | 21 | |
| | 22 | * If you run the client with the `-allow_remote_gui_rpc` command line option, it will accept connections from any host (subject to password authentication). |
| | 23 | * You can create a file '''remote_hosts.cfg''' in your BOINC directory containing a list of allowed DNS host names or IP addresses (one per line). These 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. |
| | 24 | |
