Changes between Version 2 and Version 3 of SecurityIssues
- Timestamp:
- Apr 8, 2008, 7:57:35 AM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
SecurityIssues
v2 v3 50 50 '''Intentional abuse of participant hosts by projects''' 51 51 52 BOINC does nothing to prevent this (e.g. there is no 'sandboxing' of applications). Participants must understand that when they join a BOINC project, they are entrusting the security of their systems to that project. 52 BOINC uses account-based sandboxing: applications run under a specially-created account 53 (Mac/Linux version 5.4+, Windows version 6+). 54 If your system's file and directory permissions are set appropriately, 55 applications will have no access to files outside of the BOINC directory. 53 56 54 57 '''Accidental abuse of participant hosts by projects''' 55 58 56 BOINC prevents some problems: for example, it detects when applications use too much disk space, memory, or CPU time, and aborts them. But applications are not 'sandboxed', so many types of accidental abuse are possible.Projects can minimize the likelihood by pre-released application testing. Projects should test their applications thoroughly on all platforms and with all input data scenarios before promoting them to production status.59 BOINC prevents some problems: for example, it detects when applications use too much disk space, memory, or CPU time, and aborts them. Projects can minimize the likelihood by pre-released application testing. Projects should test their applications thoroughly on all platforms and with all input data scenarios before promoting them to production status.