Originally posted by: Rattledagger
Well, if you installs BOINC as service, only installing user/admins has access to the BOINC-directory...
For anyone that does have read-access to the BOINC-directory, they can easily find the account-key for a project, and can therefore login to the web-site and change whatever they wants. No, they don't get your password, but since they can after logging-in with the account-key edit both email-address and set a new password, in reality they have full control...
As for gui_rpc_auth.cfg, for extra security-reasons this file is always generated if not present in v5.2.x, with a random password. You can still use BOINC Manager to monitor/control the local computer without knowing this password, but other users that does not have read-access to BOINC-directory will not manage to read the password-file so will fail to connect even on local computer, if they don't know the password.
You can edit gui_rpc_auth.cfg and set a password of your choise, and even a blank password. But, if you deletes the file, next time you re-start BOINC it's re-generated.
For connecting remotely from another computer, only computers/ip-address listed in remote_hosts.cfg is allowed remote connection-access.