DJRumpy wrote:A bit surprised at the length of time they needed to plug those holes.
Apparently what's being done goes beyond just "plugging holes", some likely just more time-consuming than difficult processes, and the general public isn't going to be informed of all the details.
If Apple could have better anticipated and prepared for handling an incident like this with less severity and downtime it's more disappointing than surprising to me that they didn't, but understandable when finite resources, legacy infrastructure, and other factors (possible negligence included) contribute to increased vulnerability risks.
Can't believe that researcher didn't take a better path to get the info to Apple rather than just hacking in and causing how many weeks of outages?
All that's still a hearsay report of what happened, not definitive evidence. There are plenty of unanswered questions remaining between what "that researcher" has claimed and reality even if he's been telling the truth. One speculation is that he started off as a well-intending white hat hacker who, for whatever reasons (naivety, ego, et al.), didn't heed its rules and crossed into grey/black hat territory, then tried to backpedal after he got in too deep. Inconsistencies with his supposed actions and statements seem supportive of that sort of explanation.
the beta app works fine.
Cool!