A little birdy at Apple told me that my plan detailed in the previous post won’t work at all, since Software Update will (for obvious security reasons) refuse to install any update packages not signed by Apple.
Oh, well. Back to the drawing board!
This article was published on Thursday, November 15th, 2007 at 2:50 pm.
A little birdy at Apple told me that my plan detailed in the previous post won’t work at all, since Software Update will (for obvious security reasons) refuse to install any update packages not signed by Apple.
Oh, well. Back to the drawing board!
If you're looking for something specific then give the search form below a try:
The Conversation {2 comments}
While I applaud the effort, I think what you have now is perfect in terms of interface. Adding a pref pane and all these features feels a little bloaty. I remember reading somewhere, but can’t seem to find it now, that the whole point of Sparkle was to give uniform and efficient software update to apps without even revealing the name “Sparkle” to the user…its goal was to be completely invisible from being something separate from the app. The goals of Sparkle 2 seem to be completely opposite from this.
obvious security reasons? Obviously, an update should be signed by the same people who signed the original version (except that this is hard to get right all the time…). If I wouldn’t trust a third-party update to Apple software, why should I trust an update from Apple for third-party software? (of course, maybe “Software Update” means “Apple-software Update”, which it does…)
Leave a Comment
You can follow any responses to this entry via its RSS comments feed. You can also leave a trackback if the inclination is there.