I believe that BOINC can run as a service with a limited account that has been granted full access to the BOINC directory.

---

BOINC WIKI

May have some answers here Links to Documents by Project or How I found out all the Stuff I Needed to Know About BOINC

---

Semper Eadem
So long Paul, it has been a hell of a ride.

Park your ego's, fire up the computers, Science YES, Credits No.

Then running BOINC as service it will start (and run) as NETWORK_SERVICE user.

---

.... answered wrong question ....

---

You need a second life? Seconlife.com

We are basically allowing seti, or Predictor, or whatever project you are running full access to execute any code on our system. What would happen if an attacker compromised one of the project servers and used it to distribute malicious code to all the clients? Is there a way to protect ourselves on the client side if a disaster like this were to occur? My first guess would be to run the client service as a limited user, but I don't know if that will make Boinc unusable. Has anyone else given any thought to this? How can we make the Boinc client more secure on our ends?

---