191–200 of 279 posts
Earlier quoted context omitted.
Hahaha on Yahoo we called it booting.
On AOL we called it "punting", and the apps that facilitated it were the first reason I ever wanted to code.
By the time AOL 3.0 rolled around, it wasn't bluescreening the machine, rather just ending the AOL process and disconnecting.
Earlier quoted context omitted.
irc has kicking / banning and kickbanning.. not necessarily booting (unless you used it as lingo) and certainly not HTML parsing.
/ping +++ATH0
Earlier quoted context omitted.
Publishing the gist of the exploit, combined with access to diffs of the patch should be enough for people to reverse engineer the exploit.
Where are they going to get access to the diffs of the patch? iOS is closed source.
Earlier quoted context omitted.
On AOL we called it "punting", and the apps that facilitated it were the first reason I ever wanted to code.
Strange nostalgic memories of "AOHell" and "LuciferX" come to mind... If I remember, a lot of them were visual basic apps that would use SendKeys() to control AOL via keyboard shortcuts. A little like the wild west back then...
Earlier quoted context omitted.
Turning off iMessage to prevent the bug is like turning off a car to prevent to consume petrol.. what a solution
Where I live nobody uses iMessage so this sounds like a good workaround :P (Yes yes I know it’s been patched already...)
Stupid question: How is the example python program actually sending an iMessage? Since Apple generally has the system locked down.
Earlier quoted context omitted.
Security researchers have to assume that if they've found a vulnerability, it's only a matter of time before the evil people will find it as well - that is if they haven't found it already. That's why all disclosures come with window - if they don't, the companies aren't under any pressure to update their systems, the exploit start being used in the wild, etc. The window is not ideal, but it is better than no window.…
Still make no sense, I agree the window is a good policy to force lazy vendors to act as they should. But what’s the point of reducing the window for nice vendors who quickly delivered a patch? This is totally counter productive. In order to incentivize vendors to deliver patches more and more quickly, good actors should profits from that extra time to secure their user base. In a ideal world that might even permit t…
Earlier quoted context omitted.
Strange nostalgic memories of "AOHell" and "LuciferX" come to mind... If I remember, a lot of them were visual basic apps that would use SendKeys() to control AOL via keyboard shortcuts. A little like the wild west back then...
Anyone recall the "SubZer0" proggie? (and who else recalls calling apps "proggies" in our kitchy chat rooms?)
Speaking as an ex-Apple employee, I'll just point out that a really malicious actor could have used this to harm some significant percentage of the installed iOS infrastructure, and done critical damage to Apple as a company with it. In fact, I don't know the percentage of users still on <12.3, but maybe they still could. A band-aid fix for this one bug should not be where they stop here.