LHC@home

Given the dynamic nature of BOINC projects, i.e., multiple clients that may be viable depending on the science that is being conducted for any arbitrary project\'s WUs, it would facilitate things for project participants that utilize firewalls, HIPS applications such as Comodo Internet Security, if project developers would digitally sign their binaries with a certificate from a trusted CA.

http://internetsecurity.comodo.com/trustedvendor/signup.php

The above URL is a link to a form that allows software vendors to request the addition of their software to the Trusted Vendor List that ships with Comodo Internet Security. This ensures their software will be automatically trusted by the application.

•Your software must be available for download by [Comodo] technicians
•Your software must be code signed with a certificate from a trusted CA (self-signed code signing certs are not acceptable)
•The \'Company Name\' you provide below matches the name of the signer on the certificate
•You must provide a valid email address

---

Per this discussion:

http://boinc.berkeley.edu/dev/forum_thread.php?id=6073

After some investigation into this matter, I determined this isn\'t all that much of an issue. While it may be ideal to have BOINC and any BOINC projects recognized by Comodo Internet Security suite out-of-the-box as trusted applications, if the BOINC projects & slots folders are desigated with \'installer / updateer\' HIPS policy, sandboxing of any BOINC project binaries is circumvented.

---