Not really. I was just taking the opportunity to share my exploration of the facts I discovered when everyone else is claiming that "obviously Apple has had this exploit for at least two weeks before doing anything about it!" meme. When I went to check if that were actually true, I found, no, it wasn't.
They were building a mountain out of a non-existent molehill from this LAST COMMENT in an obscure thread on a forum among thousands that no one, including Apple if you understood the nature of the forum, had looked at since Chethan177 wrote it more than two weeks ago.
The funny thing is that had Chethan177 reported it to Apple, he likely could have claimed a significant bug bounty worth many thousands of dollars, because Apple is paying good money for such bugs now. . . the more egregious the bug, the more they pay. They have paid up to $1 million for really significant bugs in iOS.
Thanks for the backstory. I note CoyoteDen is a “Level 1 user with 0 points” who understood the implications of what was uncovered when they saw it.
What are the chances that this is an easy-access exploit that the MacOS developers use routinely when putting together/testing updates and, in this instance, they forgot to “close the door” when that update was wrapped up?
And I want to thank you also for all the work you put into tracking down the truth behind how that angle of the story developed. Would that real journalists did as much and as fast!