Can the BOINC client be made to automatically update itself to newly released versions (e.g. we're about to move from 3.20 to 4.05) without the user having to download and install the new version?

It's my understanding that, currently, the BOINC client cannot auto-update.

However, the BOINC client --can-- auto-update the SETI client as needed.

This concept is frowned upon for security reasons.

Since BOINC downloads and runs executables, someone could maliciously "update" your Core Client to download all kinds of nice goodies to your system.

As the project applications (such as S@H) are referenced by the WUs and downloaded from Berkeleys servers on demand, the security threat isn't as great in regards to an auto update.

So as MPBroida said, the Core Client needs a manual update, the project apps are automatic.

What is the difference between updating the core and updating the project applications?
I don't think the project apps run in a sandbox. They could execute every code they want on your system.
Boinc could use the same system to update the core that is used for the project apps.
You (the user) select from which project you want your updates. The update is digitally signed by the project. If the signature is valid, the update is installed on your machine.

> What is the difference between updating the core and updating the project
> applications?
> I don't think the project apps run in a sandbox. They could execute every code
> they want on your system.
> Boinc could use the same system to update the core that is used for the
> project apps.
> You (the user) select from which project you want your updates. The update is
> digitally signed by the project. If the signature is valid, the update is
> installed on your machine.
>
I personally agree with this however there are alot of people that are more paranoid than me. Maybe after BOINC has proved itself there will be less resistance to making the CC autoudate.

On the other hand doing a major version update can be pretty devestating since all projects are reset. So maybe it is a good idea to do that manually so the user can minimize the disruption.

John Keck -- BOINCing since 2002/12/08 --