Automatic update

Questions and Answers : Wish list : Automatic update
Message board moderation

To post messages, you must log in.

AuthorMessage
Richard Hayes (Torquemada)

Send message
Joined: 15 Aug 00
Posts: 3
Credit: 230,377
RAC: 0
United Kingdom
Message 18390 - Posted: 27 Aug 2004, 20:42:14 UTC

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?
ID: 18390 · Report as offensive
MPBroida

Send message
Joined: 6 Sep 00
Posts: 337
Credit: 16,433
RAC: 0
United States
Message 18445 - Posted: 27 Aug 2004, 22:21:54 UTC

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

However, the BOINC client --can-- auto-update the SETI client as needed.
ID: 18445 · Report as offensive
Heffed
Volunteer tester

Send message
Joined: 19 Mar 02
Posts: 1856
Credit: 40,736
RAC: 0
United States
Message 18471 - Posted: 27 Aug 2004, 23:23:42 UTC
Last modified: 27 Aug 2004, 23:25:42 UTC

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.

ID: 18471 · Report as offensive
philjfry
Volunteer tester

Send message
Joined: 1 Apr 01
Posts: 9
Credit: 1,923,111
RAC: 225
Austria
Message 19047 - Posted: 29 Aug 2004, 8:31:19 UTC

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.
ID: 19047 · Report as offensive
Profile Keck_Komputers
Volunteer tester
Avatar

Send message
Joined: 4 Jul 99
Posts: 1575
Credit: 3,582,910
RAC: 2,027
United States
Message 19103 - Posted: 29 Aug 2004, 14:36:54 UTC - in response to Message 19047.  

> 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 --
ID: 19103 · Report as offensive

Questions and Answers : Wish list : Automatic update


 
©2018 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.