Changes between Version 1 and Version 2 of RpcAuth


Ignore:
Timestamp:
Apr 25, 2007, 9:35:31 PM (18 years ago)
Author:
Nicolas
Comment:

Required manual changes to automatic conversion.

Legend:

Unmodified
Added
Removed
Modified

  • RpcAuth

    v1 v2  
    33
    44== Remote control of the BOINC client ==
    5  The BOINC core client typically is controlled by the [ManagerAdvanced BOINC Manager] running on the same machine:
     5The BOINC core client typically is controlled by the [ManagerAdvanced BOINC Manager] running on the same machine:
    66
    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:
     7[[Image(http://boinc.berkeley.edu/gui_auth.png)]]
    88
    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)]]
     9The 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:
     10
     11[[Image(http://boinc.berkeley.edu/gui_auth2.png)]]
     12
     13You can use [http://boinc.berkeley.edu/addons.php add-on programs] such as BOINCView to control many BOINC clients at once:
     14
     15[[Image(http://boinc.berkeley.edu/gui_auth3.png)]]
     16
    1017== 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:
    1218
     19Since 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:
    1320
    1421 * 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.
    1522 * You can specify a set of hosts from which RPCs are allowed. By default, RPCs are allowed only from the same host.
    1623
    17  A GUI RPC is handled only if it passes both levels of protection.
     24A GUI RPC is handled only if it passes both levels of protection.
     25
    1826== 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:
    2027
     28By 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:
    2129
    2230 * 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).