Sounds like you were OK with not having a jailbroken iPhone.
I'll wait for official word from Dev-Team, thank you very much.
i took one for the team!
i'll *attempt* a reJB later when i get home.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Releases iPhone OS 3.0.1 to Address SMS Security Vulnerability
- Thread starter bmacir
- Start date
- Sort by reaction score
i took one for the team!
i'll *attempt* a reJB later when i get home.
I haven't JB-d in a month so no worries, but thanks tho.
I can confirm on a 32GB iPhone 3GS Black:
- Tethering still working just fine
- Appears to have fixed issue wherein certain icons were mismatched/disappeared
W00t - I'm a happy secure camper
It seems unlikely that such a threat is in the wild at the moment. I would encourage everyone to update as soon as possible though.
Installing now but I guess we can only wish. I have bag lag on my 3G after 3.0 also... I wish they fix that issue...
James
The computer I use to sync with my phone is in repairs, so it'll be a while until I can update.
Yes, set the phone to airport mode.
Never said it was practical.
Or if you want to be REALLY cynical: it takes time to create and test even a simple patch. They had to have started some time ago. Maybe they even finished some time ago! But they thought a release just AFTER the "big fear" announcement would be worth more headlines and make a good PR impression
Whereas a release beforehand would go largely unnoticed by the press.(I'm not really that cynical. Probably.)
You're reading something I didn't say, I think
He's a good guy for catching the flaw, and a good guy for notifying the vendors secretly as he should have. My praise had nothing to do with how he "makes Apple look."
Also I don't know HOW he made the recent public presentation, and I have no opinion on that stage.
Kudos to Google as well. The correct headline, then, seems to be: "Microsoft and wireless carriers late to fix serious flaw in Windows Mobile, while Apple and Google patch promptly."
As for Apple releasing this one day after the announcement:
1. Did Apple ignore the issue and then suddenly fix AND test the fix last night? Or have they been working on it beforehand? The latter is far more likely.
2. How could the public announcement NOT prompt the release of the fix? Apple may have been planning to include it with some other fixes that aren't ready today. Instead, they released the fix alone. Seems sensible.
I agree that after they were notified Apple probably started working on it right away.
As the bug was not known publicly, they may initially plan to release this with 3.1 or before 3.1 with some other updates.
But since it hits the news, they have no choice but to release it now.
However, I also think they should have released it earlier as this bug can cause serve damage easily.
Or if you want to be REALLY cynical: it takes time to create and test even a simple patch. They had to have started some time ago. Maybe they even finished some time ago! But they thought a release just AFTER the "big fear" announcement would be worth more headlines and make a good PR impression
(I'm not really that cynical. Probably.)
Yeah because they had a flippin' month!
Apple could have at least had a little fun and added one of the 3.1 features into this update
They could have intentionally slipped MMS into the update, and then looked at AT&T and said "Oh! My Bad!" Hahaha.
funny how you think Apple is holding back the MMS
its all ATT nothing to do with apple.
Yeah because they had a flippin' month!
Also to note: right or wrong, Apple (and NOT just Apple) does often consolidate multiple fixes into a single patch and then release them all together. (Which is nice for the user not getting constantly badgered with little updates--just so long as the flaws aren't already BEING exploited of course!)
That's a more likely explanation for taking a month to release, rather than "they tried for a month and couldn't fix it" or "they didn't even try to fix it."
However, whatever their release plans were, they went ahead and released this one fix now instead. Exactly as they should have.
Does 3.0.1 fix the notorious wifi problem? I am still on 2.2.1 after 3.0 disaster and my third replacement iPhone...
Oh man. I'd forgotten to upgrade to the newest release of iTunes. :-( Had to upgrade iTunes and then restore everything on my phone like new. It's going to take a long, long time.
Wirelessly posted (Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/530.17 (KHTML, like Gecko) Version/4.0 Safari/530.17)
All thi8s talk about "What took Apple so long"...
I have a strong suspicion Apple had this fix and WAITED for today to release it.
I think it's PR spin. They've taken this morning's news story of "iPhone is vulnerable to a virus" and made the evening news story "Apple responds immediately to iPhone threat".
It's really only us geek folks who know Apple was told about this 6 months ago and could have patched it a long time ago.
I really think this is spin. Like the way the recently handled Steve Jobs liver transplant news. THAT could have been a media-storm. Instead, it was handled (and timed) beautifully. It ended up really being a non-story.
Who's doing PR there now? Someone new?
All thi8s talk about "What took Apple so long"...
I have a strong suspicion Apple had this fix and WAITED for today to release it.
I think it's PR spin. They've taken this morning's news story of "iPhone is vulnerable to a virus" and made the evening news story "Apple responds immediately to iPhone threat".
It's really only us geek folks who know Apple was told about this 6 months ago and could have patched it a long time ago.
I really think this is spin. Like the way the recently handled Steve Jobs liver transplant news. THAT could have been a media-storm. Instead, it was handled (and timed) beautifully. It ended up really being a non-story.
Who's doing PR there now? Someone new?
Does 3.0.1 fix the notorious wifi problem? I am still on 2.2.1 after 3.0 disaster and my third replacement iPhone...
That--and the notorious GPS problem--will need to wait for 3.1 I expect, and that means September according to a past MR posting. (And both have affected me
) Getting a new iPhone may help, since the problem doesn't affect every iPhone. But I've resisted asking for that since it's a) a waste, b) might not help and c) a royal pain for me 3.0.1 is a single-purpose fix, possibly planned to include other things that aren't ready yet. But this one fix was needed now, since the exploit was announced to the public (and thus to crackers).
I haven't JB-d in a month so no worries, but thanks tho.
I can confirm on a 32GB iPhone 3GS Black:
- Tethering still working just fine
- Appears to have fixed issue wherein certain icons were mismatched/disappeared
W00t - I'm a happy secure camper
I was hoping they'd fix the icon problem.
Safari is "snapier", and am i just a ditz or has safari always had a landscape keyboard?
The tethering was still there BUT when i turned on tethering, and then i pressed back to return to the network settings, IT WAS GONE! But benm.at still works, meaning it still lets you go to the site. I will now try to download and install tethering again.
EDIT: I reinstalled tethering on my 32gb 3GS and it is working fine now.
The tethering was still there BUT when i turned on tethering, and then i pressed back to return to the network settings, IT WAS GONE! But benm.at still works, meaning it still lets you go to the site. I will now try to download and install tethering again.
EDIT: I reinstalled tethering on my 32gb 3GS and it is working fine now.
I won't say you're a ditz but it has been there and the snappiness is likely your "mind playin ticks on ya"...
Nope. Just sloppiness. That's why they didn't return calls, until they were publicly embarrassed. It probably took them less than a week.
Apple has always been the sloppiest of the majors, regarding security.
From a Swiss survey in 2008:
"...During the period studied, between 2002 and 2007, Microsoft had 658 high- and medium-risk vulnerabilities, compared with 738 for Apple, the paper says.
The revived popularity of Apple's products, the researchers suggest, may have left Apple unable to keep up. "Comparing the number of unpatched vulnerabilities per vendor for the period since January 2002 we observe a striking difference between Microsoft and Apple," the report says. "On average, Microsoft succeeds to keep the average number of unpatched vulnerabilities below 20 at a steady number. On the opposite, Apple seems unable to stabilize the number of unpatched vulnerabilities in recent years. We observe a steady increase in recent years for Apple. It seams [sic] that Apple's security processes and resources cannot cope with the side-effects of the increased popularity of their products..."