Linked by Thom Holwerda on Mon 5th May 2008 21:00 UTC
Thread beginning with comment 313242
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
More News »
Sponsored Links



Member since:
2006-08-14
Or alternatively, the developer/maintainer or whoever does the bundling can simply use some sort of cryptographic key, which the installer uses to confirm the new bundle is indeed from the same source as the already installed bundle.
Basically, the problem you're trying to solve is intrinsic to any form of installation, not only the idea posted in this article, so whatever solutions exist already can be used without any need for centralised administration.
If I recall correctly, zero-install used some crypto-signing for something similar.