Diego’s Rants by » The digital certificate breakage
The digital certificate breakage
So um. some weeks ago I released a fresh story of MediaInfo Mac with individual fixes on my own conventions, with also a newer assemble of the MediaInfo Lib at submit Jerome Martinez, and, at large decisive, a newer story of Sparkle (the memorable framework that i capitalize on in the direction of the automated software updates).
To hightail it a exceedingly large fairy allegation quite unplentiful, Sparkle changed an ignominious behavior: Now each and every update that I make available has to be signed with a digital certificate, which is nothing but considerable, because it gives an surfeit layer of safe keeping in the direction of the ending users.
I pacify had the members to manifest to the users a keen dialog informing them rat on my typographical error and kindly asking to update manually, but down reciprocate that, i pacify can look to that a LOT of people is pacify using the disciplined story (0.7.7.58), which leads me to the following conclusion:
Most people devise NOT upgrade their software unless the criticize is thoroughly remiss and as ABC, not down reciprocate users of MediaInfo which are customarily to the ground the “Average Joe”.
Bad fairy allegation are that I thoroughly missed that in the main in Sparkle’s make available docs, so I released an update without the certificate, and from there on, users were stuck on that story without the capacity to update.
This can be seen on the capitalize on statistics that i screen (which I did reset some hours ago btw, just to some preparations in the direction of the upcoming MediaInspector beta) where you can look to that there are pacify a LOT of users stuck on 0.7.7.58.
If you are on Mac OS X 10.5 “Leopard” or newer, lone bug the latest story here.
So to sum come to things up:
If you are using Mac OS X 10.4 “Tiger”, the latest story that you can capitalize on is 0.7.17.3, bug it here.
Cheers!.
Diego.