111–120 of 279 posts
This is fixed in iOS 12.3 [1] and macOS 10.14.5 [2], both released on May 13th. As Natalie noted on the ticket, turning off iMessage will also prevent the bug. [1]: https://support.apple.com/en-us/HT210118 [2]: https://support.apple.com/en-us/HT210119
Turning off iMessage to prevent the bug is like turning off a car to prevent to consume petrol.. what a solution
Earlier quoted context omitted.
That sounds like a logic flaw because iPhones and most other devices like it will normally auto update after a short while. I think more people will rely on that feature than browse, uh, bugs.chromium.org... This view of it will assist hackers in getting a head start before the auto update cycle gets to your device and you're notified. And if you're hit but something like this before that, your iPhone will no longer…
It was patched in march.
Earlier quoted context omitted.
The problem isn’t that the bug itself will cause data loss - it’s that you have no way of using the phone because of the boot loop unless you wipe. I’m not entirely sure how you’d go about updating the phone without booting into it, but I think it is possible, and that would be one way to avoid losing all your data due to the bug.
One of the comments on the bug has the answer: For testing purposes, there are three ways that I found to unbrick the device: 1) wipe the device with 'Find my iPhone' 2) put the device in recovery mode and update via iTunes (note that this will force an update to the latest version) 3) remove the SIM card and go out of Wifi range and wipe the device in the menu
Earlier quoted context omitted.
Yeah but maybe it would be nice for users to keep that extra time in order to maximize the probability that they have actually updated software at disclosure time. Disclosing in advance is a bad policy, it will just incentive good behaving vendors that update fast to delay full description of their changelog for security reasons because you put their users at unnecessary risks.
The fix has been available for almost two months. Don't iOS updates hit the 50% adoption mark within two weeks?
Earlier quoted context omitted.
Apple sells privacy and security so they should live up to the standards they have set for themselves[1]. They were actively misleading peoplebby running advertisements claiming MACs don't get virueses[2]. [1] https://www.forbes.com/sites/daveywinder/2019/06/21/new-crit... [2] https://www.wired.com/2012/06/mac-viruses/
Your second link is an article from 2012 that says Apple stopped saying Macs can’t get viruses...
Moreover Apple only stopped after misleading users for a long time and that also hapenned after high profile incidents as explained in the article.
This brings back old memories from hardening the sms/text parsers of feature phones of yesteryear. There it wasn’t entirely uncommon that when you sent a malformed sms-deliver PDU (e.g. text message) to the phone and crashed parser that tried to decode it, it took also the phone down before it could ack the message back to SMSC. Which of course meant that as soon as phone was turned on and it registered to network, t…
Earlier quoted context omitted.
It's a sliding scale which depends on the user's competence and not just the hardware. To a completely non-technical person, a hard lock-up is "bricked" even if it could be fixed by pressing buttons. To a normal user, a borked ROM is "bricked" even if it could be fixed by plugging into a computer and re-flashing. To a power user, a busted bootloader is "bricked" if it stops them flashing a ROM, even if it could be fi…
The only purpose of the word’s existence is to define an entirely unrecoverable state. Crash loop or hung on startup describes the state. It is by definition not bricked if it can be recovered.
Looks like the "curse of complexity" strikes again... every time I see bugs like this, I wonder if it's because of some code that tries to be a little "too smart" in trying to parse what could be arbitrary data, and forgetting some edge-case. (If you have JS disabled, you can click "View in Old UI" and then view source to see the content. I find that a bit ironic in the context of this specfic bug...)
Is this an issue of complexity or lack of isolation? More isolation means more complexity, but at the same time, this issue should crash the iMessage app itself, not the whole system. The fact that springboard even knows about iMessage structure is crazy...
You don't really need isolation if the code is so simple as to obviously contain no bugs (instead of containing no obvious bugs.)
Instead, we have a whole industry built upon encouraging the creation of things as complex as possible, and working around the problems caused by that by adding even more complexity, mainly because it means people have more to do.
http://countercomplex.blogspot.com/2014/08/the-resource-leak...
(No, downvotes from the complexity-brigade are not going to make me change my mind either.)
Earlier quoted context omitted.
Your second link is an article from 2012 that says Apple stopped saying Macs can’t get viruses...
Not getting a virus is a theoretical impossibility so Apple claiming the contrary is dishonest. Moreover Apple only stopped after misleading users for a long time and that also hapenned after high profile incidents as explained in the article.