Linked by David Adams on Wed 14th Dec 2011 15:41 UTC, submitted by bowkota
Privacy, Security, Encryption A malicious message sent to Windows Phone's message hub can disable the handset in a manner reminiscent of the "nuking" attack from the Windows 95 days. At the point the bad message is received, the phone reboots, and worst of all, it appears that the message hub application is permanently disabled. Back when people used to only use their phones to call and text, you'd perhaps think that having your phone reboot on you would be no big deal. But these days I find myself often as not composing some important missive.
Thread beginning with comment 500213
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Chicken Little says...
by japh on Thu 15th Dec 2011 19:40 UTC in reply to "RE: Chicken Little says..."
japh
Member since:
2005-11-11

And that's only if all of them have SMS enabled, are powered on and are within range of a tower before the message expires.


If you don't power on and connect to the network before the SMS expires you essentially have no phone anyway. ;) It's not a typical scenario for any of the phone owners that I know of anyway.

Reply Parent Score: 2

RE[3]: Chicken Little says...
by glarepate on Fri 16th Dec 2011 06:56 in reply to "RE[2]: Chicken Little says..."
glarepate Member since:
2006-01-04

If you don't power on and connect to the network before the SMS expires you essentially have no phone anyway.


Yeah, it would be better to have a phone but with no SMS. Or to have an iPod Touch with a SIP client app.

It's not a typical scenario for any of the phone owners that I know of anyway.


Less typical than getting a text, having your phone die and then being unable to get a text after rebooting? There have been times when I wished I couldn't get an SMS and even more so an MMS, but I have changed carriers twice since then. (o;)

Reply Parent Score: 2