Live data from Hacker News

iMessage: Malformed Message Bricks iPhone

bugs.chromium.org

151–160 of 279 posts

Re: iMessage: Malformed Message Bricks iPhone

#151
post #34

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…

> 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.

By yesteryear do you mean the present and feature phones do you mean current android phones? Some models are still vulnerable to a text-of-death.

https://poetengineer.postach.io/post/deleting-the-text-of-de... not my blog, but the same problem happened with my mother in law's phone. The phone becomes unusable because of a stream of org.android.phone application has stopped messages and the only thing to do is use adb to delete all texts, until it comes in again. I was never able to pin down the exact problem.

Edit: Sorry, I didn't mean to come off as snarky, but I just wanted to 1) point out that there are still issues with decoding SMS and MMS messages, even in some modern phones and 2) provide a link to anyone who encounter the same issue as it was very frustrating for my MiL and very frustrating until I figured out I could just wipe all SMSes with adb.

Re: iMessage: Malformed Message Bricks iPhone

#152
post #104

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...)

I never understood this, why would anyone want to deal with ANOTHER app to do messaging? iMessage is built in, integrated, and has end to end encryption. What more functionality are people clamoring for?

Re: iMessage: Malformed Message Bricks iPhone

#153
post #136

Earlier quoted context omitted.

Hahaha on Yahoo we called it booting.

Doesn't that date back to IRC?

irc has kicking / banning and kickbanning.. not necessarily booting (unless you used it as lingo) and certainly not HTML parsing.

Re: iMessage: Malformed Message Bricks iPhone

#154
post #104

Earlier quoted context omitted.

Where I live nobody uses iMessage so this sounds like a good workaround :P (Yes yes I know it’s been patched already...)

I never understood this, why would anyone want to deal with ANOTHER app to do messaging? iMessage is built in, integrated, and has end to end encryption. What more functionality are people clamoring for?

> What more functionality are people clamoring for?

All those features in a market where lots of people you'd be chatting with are on Android, I'd suspect.

Re: iMessage: Malformed Message Bricks iPhone

#155

Lazy developers throw exceptions, good developers return errors. Exceptions should be exceptional. I'll use URL to this bug in my next comment-holywars to prove this point. Yes, it takes much less code to throw an exception in hope some code will catch it, but while compiler (not runtime) doesn't check it - this technique is not safe. So we should return errors, check them and handle - sometimes it means returning er…

You want to write explicit error handling for every possible case of runtime type errors in a dynamically typed language? The "unrecognized selector sent to instance" exception is not thrown in the hope that someone will catch it. It's intended to be a fatal error reporting a precondition violation.

That’s what secure coding guidelines say to do. It’s called “input validation”. For example here’s Apple’s: https://developer.apple.com/library/archive/documentation/Se...

Especially important on methods called on launch, if a crash would cause a problem.

(Swift or other strongly typed language would help here.)

Re: iMessage: Malformed Message Bricks iPhone

#156

   bplist00ÔX$versionX$objectsY$archiverT$top † ¦U$nullÓ 
  WNS.keysZNS.objectsV$class¢
   €€¢€€€RanVldtext¢ËqÒZ$classnameX$classes\NSDictionary¢XNSObject_NSKeyedArchiverÑTroot€#-27>DKS^ehjloqsux„‰”ª­¶ÈËÐ                             Ò

Re: iMessage: Malformed Message Bricks iPhone

#157
post #104

Earlier quoted context omitted.

Where I live nobody uses iMessage so this sounds like a good workaround :P (Yes yes I know it’s been patched already...)

second that. half of my friends using iphones dont enable imessage. thus penetration (in my circles) is way too low to make it useful.

Considering it's enabled by default, i'm really curious why you would want to do that.

Re: iMessage: Malformed Message Bricks iPhone

#158
post #55

Earlier quoted context omitted.

“Difficult [for someone] to recover” should not be a partially overlapping state as “bricked”. I had a EdgeMax Lite router which has a propensity for the flash storage to get corrupted at which point it fails to boot. The fix is to buy a particular model of USB flash drive, and image it with a specific .img file. Open the case and replace the flash stick, then boot holding the reset button. It was a somewhat difficul…

Not a brick if you have to replace a storage device. Is it a brick if you have to replace a motherboard? Would replacing a motherboard not have fixed your xbox? (Surely the commercial availability of a part isn't the deciding factor in whether something is a brick, right?)

Commercial availability of a part is absolutely a factor in deciding whether something is a brick! I.e. some large expensive machine is bricked because the manufacturer refuses to sell you a small proprietary part without which the machine is entirely non-functional.

It’s a fairly frequent pattern where an IoT device becomes a brick because an API shuts down. Similarly, if you can’t replace a crucial part because the manufacturer won’t sell it to you, that would brick a device. If the device is cheaper to replace than to repair, then it is bricked (the Xbox).

A brick must be entirely non-functional and simply not worth repairing. It’s supposed to be a less vulgar version of FUBAR.

There are rare stories of extraordinary lengths that a maker will go to (such as fabbing your own custom parts, or standing up a private version of an API and DNS hijacking requests from the device in order to make it function again) in order to “un-brick” a device. The defining trait of these stories is that something new is invented in order to make the device function again.

Re: iMessage: Malformed Message Bricks iPhone

#159

Earlier quoted context omitted.

I never understood this, why would anyone want to deal with ANOTHER app to do messaging? iMessage is built in, integrated, and has end to end encryption. What more functionality are people clamoring for?

> What more functionality are people clamoring for? All those features in a market where lots of people you'd be chatting with are on Android, I'd suspect.

See samoa below, half of his friends using iphone disable imessage??? It's nonsensical. iMessage works wonderfully.

Re: iMessage: Malformed Message Bricks iPhone

#160

Earlier quoted context omitted.

Did iOS ever have a “virus”?

No, never iOS is deisgned by Gods themselves. https://www.theiphonewiki.com/wiki/Malware_for_iOS

Not all malware is a "virus."

Has iOS ever had anything where one app could "corrupt" other apps?

Post reply on HN