Changes between Version 11 and Version 12 of ClientSetupWinSix
- Timestamp:
- Jun 16, 2008, 11:17:37 AM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ClientSetupWinSix
v11 v12 8 8 9 9 This document describes the design of the BOINC Windows installer for version 6. 10 See also the [ClientSetupLogicWinSix implementation details].10 See also the [ClientSetupLogicWinSix implementation notes]. 11 11 12 12 == New features == … … 24 24 25 25 * '''Public''': all users on the host can control BOINC (i.e. attach/detach projects) using the BOINC Manager. 26 * '''Private''': Only the user who installed BOINC or an administrator can control BOINC. Users can be allowed to control by adding them to a'boinc_users' group. When other users run the BOINC Manager, they'll get a dialog saying to contact the administrator to add them to the 'boinc_users' group.26 * '''Private''': The only users who can control BOINC are: the installing user; administrator; members of the 'boinc_users' group. When other users run the BOINC Manager, they'll get a dialog saying to contact the administrator to add them to the 'boinc_users' group. 27 27 28 28 == Account-based sandboxing == … … 37 37 * It limits the damage that can be done by buggy or malicious applications 38 38 * It limits the damage due to bugs or network security vulnerabilities in the core client. 39 * By default non-administrative accounts cannot create globally named shared memory segments, thereforekeyboard and mouse activity could not be monitored without setting up an account with that additional user right.39 * Keyboard/mouse detection works with multiple users. By default non-administrative accounts cannot create globally named shared memory segments, so keyboard and mouse activity could not be monitored without setting up an account with that additional user right. 40 40 41 41 In secure mode, the BOINC client is started at system boot time by the service control manager.