On Thu, 31 Jan 2019 18:52:54 +0000 (UTC), badgolferman wrote:
> To me this is a more egregious security flaw than the FaceTime bug.
To me, both indicate two things, one for sure, the other implied:
1. For sure, Apple _should_ have done better testing (that's a fact!)
2. It's implied that Apple really doesn't care about testing (inference)
What's clear is this:
3. When the news breaks - then Apple MOVES FAST!
Inference:
o It seems Apple only cares when their IMAGE is at stake.
> 1. There are supposed to be security credential checks in place when
> accessing servers and it appears this was easily defeated.
Yup. These FACTS exist, time and again.
o Apple has plenty of _easy_ to test bugs
o The fact they exist, is proof Apple does not sufficiently test for them
Those are obvious facts no intelligent adult could possibly deny.
> 2. A person has no real ability to safeguard their online account
This is a valid point that the user must _trust_ Apple on the online stuff.
HINT: It's why I don't store anything on Apple servers (if I can help it).
> 3. Apple hid this flaw and never made it public knowledge until they
> were confronted about it.
This is yet another indication of the inference below:
o Apple doesn't care about actual security as much as the IMAGE of it.
> At the very least they should have made a
> general statement about "rare cases" and described the enhanced
> security precautions taken.
Apple is not known for "giving a shit" about their customer.
o Witness the battery fiasco ... as just one glaringly obvious example.
1. Apple "secretly" throttled, & only admitted it _after_ the news broke.
2. Apple then lied (and got caught in a bunch more lies) about it.
3. In the end, Apple blamed everyone but themselves for what happened.
And not a single head rolled (as far as I know).
o The inference is that this was typical Apple Marketing Strategy
The strategy, in layman's blunt terms, is:
o Apple doesn't give a shit about the customer nor about the product
o Apple only cares about the IMAGE of the product
> Some will argue you don't want to publicize your weaknesses, but I say
> when you admit a shortcoming and show improvements people trust you
> even more.
Apple has a long sordid history of not being trustworthy
o For example, they shipped the broadcom bug, claiming the release was a
"security update" even when they already had the Broadcom-supplied bugfix
in hand _before_ they shipped the 10.x release - and then, only about a
week (or was it 10 days?) later, they had to beg everyone to destroy that
release since they _knew_ when they shipped it that it has security holes
in it so big you could drive a yellow school bus through them.
*That proved that "schedule" is more important than actual security.*
Remember, Craig Federighi said the same thing:
o He complained that the Marketing-driven schedule was more than the
software engineering organization could deliver on without releasing buggy
code.
What does Apple do?
o They _continue_ to be schedule driven instead of quality driven.
The proof is (endlessly) in the taste of the pudding.
*The sheer number of easy-to-find egregious Apple bugs is astounding!*
It's the main reason I state that the Apple user wants to _feel_ safe
o And they feel safe _merely_ by frequent releases
It's exactly why I call it the "diarrhea that is the iOS release schedule".