33 | | || boinc_users || Everyone (is 'Allow everyone to use BOINC' is checked), else empty || |
34 | | |
35 | | Both account are set up so that their passwords never expire. |
36 | | |
37 | | ''The password properties will be added to !SecureCustomProperties to prevent them being logged.'' |
38 | | |
39 | | A file will be created by the installer in the BOINC data directory called client_init.xml which contains the username and base64 encoded password for `boinc_project_<ComputerName>`. The first time the client starts up after install it will read the file and store an encrypted form of the data in a new file using !CryptProtectData/CryptUnprotectData. After reading in the client_init.xml file it will be deleted. ''Can this be done with a deferred custom action?'' |
40 | | |
41 | | Each time an installation occurs, both of the account passwords will be reset and a new randomly generated password will be used. |
42 | | |
43 | | |
| 33 | || boinc_users || Everyone (if 'Allow everyone to use BOINC' is checked), else empty || |
| 34 | |
| 35 | Account passwords are managed as follows: |
| 36 | * The installer creates a file 'client_auth.xml' in the BOINC data directory containing the name and base64 encoded password of the boinc_project account. |
| 37 | * The password properties are added to !SecureCustomProperties to prevent them being logged. |
| 38 | * The password for boinc_master is managed by Windows. |
| 39 | |
| 40 | On each installation, both of the account passwords are randomly regenerated. |