Good security is multi-layered. The BOINC system attempts to maintain good security practices at all levels.

Project Security

The BOINC system requires that you run executables provided by a third party — the company or institution running the project. Each project typically publishes their own security and privacy policy. Measures may include:

  • Regular security audits of project code.
  • Enabling or requiring SSL communication with project servers.
  • Virus scanning of project files.

BOINC has its own usage and privacy policy?.

BOINC Security

Official builds of the BOINC client software are digitally signed with the University of California, Berkeley code signing key. Use an official build, or build from source yourself. Only use third party builds of the BOINC software if you trust the third party.

BOINC uses digital signatures to allow the core client to authenticate project executable files. Hashes of downloaded files guard against accidental corruption.

User Security

You can limit the risk from malicious or insecure project code by running BOINC with reduced permissions. This technique is called sandboxing. Some BOINC platforms (currently Mac OS X and some Linux ports) provide sandboxing by default. However, you should check that your exposure is limited and reduce it if necessary.

Last modified 14 years ago Last modified on Nov 8, 2007, 12:14:41 AM