Changes between Version 2 and Version 3 of RpcAuth


Ignore:
Timestamp:
Aug 9, 2007, 7:27:44 PM (17 years ago)
Author:
Nicolas
Comment:

Anchors

Legend:

Unmodified
Added
Removed
Modified
  • RpcAuth

    v2 v3  
    1515[[Image(http://boinc.berkeley.edu/gui_auth3.png)]]
    1616
    17 == Access control for GUI RPC ==
     17== Access control for GUI RPC == #gui_rpc_auth
    1818
    1919Since 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:
     
    2424A GUI RPC is handled only if it passes both levels of protection.
    2525
    26 == Allowing RPCs from remote hosts ==
     26== Allowing RPCs from remote hosts == #remote_hosts
    2727
    2828By 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: