I guess they wanted to make it clear they had an issue, fixed the issue, and publish that the issue was resolved and that no further issues were found.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Responds to Developers Regarding Expired Mac App Store Security Certificates
- Thread starter MacRumors
- Start date
- Sort by reaction score
I guess they wanted to make it clear they had an issue, fixed the issue, and publish that the issue was resolved and that no further issues were found.
This is what you get for running signed apps on your desktop. Nothing like being about to give a presentation to 100 people and having Keynote refuse to launch because of an expiration date on a freaking certificate.
Oh boy...
At this point I really have to wonder what's going so horribly wrong in Cupertino that they don't think things through and don't look at older software at all...
A new low for their quality assurance...
Good example of how the App Store is a consumer product that's able to run on work machines and "pro equipment" (or what's left of it).I was on a 10h flight when this effect kicked in. Uncool when you're offline and apps you paid for simply stop working
There should be an easy way to - without playing with date and time on your system clock - ignore the certificate issue.
Hell, I can do it in my browser and it's easily accessible.
Glassed Silver:mac
This just in: "Apple Writes Poorly Written Apology Letter to Developers Regarding Mac App Store Bug"
It's not an apology. It is an informational letter telling them what happened. Importantly, it tells them that some developers are using a crappy old version of OpenSSL that can't verify more secure certificates. (In this context, "secure" means "harder to forge and to get an app for free with a forged certificate").
With the sunsetting of SHA1 it's not surprising that Apple would be moving it's certificates to SHA2.
That said this was a little league mistake of not QA'ing the change first! These forced upgrades and growing library of broken old software is starting to get very tiresome.
If you have so little trust in Apple that you actually think this was more than a simple mistake, then yes. Sell all your Apple products and go completely Windows and Android. That said, there are no signs of this being any more than an honest, if not boneheaded, mistake.
This is a good point. We don't actually "purchase" applications from the App store - they will all "expire" and stop working at some point - we "rent" them. Making a note to myself to get things directly from the developer whenever possible (and no included time bombing like you get from the Mac App store).
This. Looks like a plain oversight on their end.
Simple as "it's not as simple as it once was". Apple's job of managing everything that they do has become 10x harder. Something is bound to not "just work" once in a while. Not making excuses for Apple, they clearly are making missteps, but as a software developer and server administrator, I know first-hand that over time, as you build more and more, it gets significantly harder to manage.
All for a free app or one you paid < $3 for. Oh, the horrors! If you paid more than that, contact the developer. If you read the user agreement, you will see that this is all covered in it. You are LUCKY if the app is UPDATED to run on a new system.
As an independent developer myself, I find the entitlement to perpetual free lifetime upgrades crazy. How are we supposed to live from a one time purchase of an app which in some cases is the less than price of a mcdonalds happy meal. Even more expensive software takes time and effort to produce. Most folks have no problem throwing down $1k a year on a new iPhone, but balk at the idea of ever having to pay an update fee for an app which was purchased eat some point in the distant past. Apple is the biggest company in the world with unlimited money and resources, most indie devs are not. a 2 year lifespan for an app is more than generous i think.
I would like to humbly suggest that the two of you are talking past each other. As a user affected by this issue in a rather painful way. I am running MacFamilyTree version 6 (genealogy software) on a white plastic MacBook with 10.6.8. Everything has worked perfectly since 2011 and my database now contains over 3000 people. When the certificate issue arose, my copy of MacFamilyTree broke. But, I cannot re-download it from the App store (where I purchased it) because it contains version 7 and that version is not compatible with 10.6.8.
Now, when MacFamilyTree version 7 was released, the developers indicated that it would cost an additional 40 dollars for those of us using version 6, but we we warned not to upgrade if we were staying on OS 10.6.8. So, I stayed with the legacy software since it Just Worked.
When my old plastic MacBook breaks, I will buy a new Mac laptop with whatever is the latest system software. And, I fully expect to buy version 7 (for 50 dollars now) as a way to support the developers.
But, that said, and this goes to the heart of the issue: it is altogether crazy that one hidden update from Apple has cracked my perfectly functioning software ecosystem. Now I am SOL where my genealogy work is concerned.