{"id":1850,"date":"2009-07-31T08:25:21","date_gmt":"2009-07-31T16:25:21","guid":{"rendered":"http:\/\/www.perivision.net\/wordpress\/?p=1850"},"modified":"2009-07-31T08:38:43","modified_gmt":"2009-07-31T16:38:43","slug":"update-iphone-should-be-secured-tomorrow-yeaaa-for-noise","status":"publish","type":"post","link":"https:\/\/www.perivision.net\/wordpress\/2009\/07\/update-iphone-should-be-secured-tomorrow-yeaaa-for-noise\/","title":{"rendered":"UPDATE: iphone should be secured tomorrow. Yeaaa for noise!"},"content":{"rendered":"

Read this in Gizmodo: Seem Apple will have a patch out to take care of the SMS hijack issue<\/a> tomorrow after knowing for .. what .. 6 WEEKS??\u00a0 Oh, but 24 hours after everyone knows about it, AND people are yelling their collective heads off for a fix, AND it gets demo’ed and released at black hat.. sure, 24 hours we’ll have a fix.\u00a0 The funny part? Apple STILL has said nothing.\u00a0 This came from its United Kingdom wireless partner O2.<\/p>\n

Now, this is going to be updated via iTunes.\u00a0 I’m guessing this will kill jailbreak, so I have to decide what I’m going to do here. Since it will take a month to fix, and 90% of the phones will be fixed, AND I’m HOPING AT&T puts a fix in at the tower level, I’m going to wait till 3.1.\u00a0 (waiting to see if the dropped calls are fixed.\u00a0 If not, by by iphone).<\/p>\n

Ok, well at least its fixed.\u00a0 In full disclosure, we were not in any real danger in the short term given that Charlie Miller and Collin Mulliner, who found the exploit took around a month to write the code. Still, just bugs me. Now, MS Mobile and Android still need to patch their phones, so we’ll keep an eye out.<\/p>\n

Still on the FAIL list? AT&T.\u00a0 The better fix would be to simply block the SMS code that can cause this issue at the tower, problem solved.\u00a0 But no, from what I’ve heard on the interwebs, AT&T did not even contact the guys who discovered this bug to ask for the string(s) to block.\u00a0\u00a0 Feh.<\/p>\n

Related Posts<\/H3>