Changes between Version 1 and Version 2 of ProjectSecurity


Ignore:
Timestamp:
Apr 24, 2007, 8:42:40 PM (17 years ago)
Author:
Nicolas
Comment:

Required manual changes to automatic conversion.

Legend:

Unmodified
Added
Removed
Modified
  • ProjectSecurity

    v1 v2  
    11= Project security =
    22
    3       Before creating a BOINC project, read about [http://boinc.berkeley.edu/security.php security issues in volunteer computing]. BOINC provides mechanisms that address the major issues, making volunteer computing safe both for you and for participants. '''If you don't use these mechanisms correctly,
    4 your project will be vulnerable to a variety of attacks.
    5 In the worst case, your project could be used as a vector
    6 to distribute malicious software to large numbers of computers.
    7 This would be fatal to your project,
    8 and would cause serious damage to volunteer computing in general.
    9 '''
     3Before creating a BOINC project, read about [http://boinc.berkeley.edu/security.php security issues in volunteer computing]. BOINC provides mechanisms that address the major issues, making volunteer computing safe both for you and for participants.
     4
     5'''If you don't use these mechanisms correctly, your project will be vulnerable to a variety of attacks. In the worst case, your project could be used as a vector to distribute malicious software to large numbers of computers. This would be fatal to your project, and would cause serious damage to volunteer computing in general.'''
    106
    117We recommend that you do the following:
    12 
    138
    149 * Secure each of your server computers as much as possible. Read and implement the [http://www.cert.org/tech_tips/usc20_full.html UNIX Security Checklist 2.0] from AusCERT and CERT/CC.