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 iOS 7.0.6 With Fix for SSL Connection Verification
- Thread starter MacRumors
- Start date
- Sort by reaction score
Lol! Mine says "Downloaded" (no file size indicated). And I haven't even updated yet. I'm still showing 7.0.4. Oh Apple iOS updates. I'm holding off on this update till further notice. I just got my 5S in January, with 7.0.4 installed. Haven't had any issues with SSL. Since hearing about this vulnerability, I've stopped using apps that use SSL. And have turned it off where I can. I've heard from some early adopters of 7.0.6, that they are already having issues with their phones after the update.
I would rather take the chance with the SSL issue, than have a crappy working phone. Since the iOS 4.x.x fiasco I had on my old 3GS (3 3GS replacements, before being upgraded to the iPhone 4 to fix the issues), I've made a point of holding off on updates unless absolutely necessary. Don't fix what isn't broke, is what I always say. And right now, my 5S works just fine. And I am self conscious about unsecure network connections. I don't use free public wifi, unless I know it's absolutely secure.
----------
You can disable auto updates in iTunes. Within your mobile devices, you manually choose to install. So basically once you disable auto updates in iTunes, you have to manually choose to update on those devices you disabled auto update on.
As for your wifi, just make sure to set up that wifi in Europe once you get there. Your iDevices should auto connect when it sees it. Otherwise it will revert to cellular data if it can't connect to the wifi. Keep an eye on the symbols when roaming. And more importantly, make sure that rented wifi connection is secure. Get it in righting if you have to. Cover your ass.
That won't disable iOS from automatically downloading an iOS update when one is available and the device is on WiFi (and is plugged in I believe).
And that's probably the most you will get. The 4S is the last of the iPhones that iOS 7 will truly function pretty good on. Older phones will get slower and slower. The 3 and 3GS can't run iOS 7.
My suggestion, wipe your 4 as new. Then reinstall each app one at a time. This should get all garbage and problematic apps off your phone. Clear out any old cache, and wipe ram. You should see some more performance boost after that. But don't expect it to be peppy again. The iOS 7 was meant to run on the 5 and 5S. But the 5S is the one that will see the most benefits.
so, this basically forces users to update to iOS version they don't want to, as to the reason why they stayed with iOS6 in the first place ?
Apart from that, wait for the patch. ?
Updated mine to 7.0.6
Wow, it's completely dead and doesn't even charge or turn on or gets recognized when connected to computer in any way?
It does for me. I'm still on 7.0.4. And only because that's what my phone came with when I bought it. I've plugged my phone to my Mac, and no download, no install. iPhone is showing an available update, and waiting for me to do it...manually. Have had it set up like that since iOS 4 (for updating through iTunes), and iOS 5 (for updating through iPhone). Not sure what you are doing wrong on your end.
----------
I haven't had any issues the last couple of updates I've done. Which I don't do very often even when it's available. I always way pros and cons for the update. If my phone is working perfectly, security or no security (this usually has no effect for me), I won't update. But when I do, I always do the following.
1. I don't update when everyone else is. I wait a couple of weeks or so. When the servers have cooled down and no connection issues that will mess up the update/download.
2. I only download. NOT download and install. When I'm ready to upload, all I have to do is do a manual update, and not have to connect to Apple server.
Most people who seem to have had issues after updates is because they had issues during the process. And they usually update when a million other users are as well. That's a good way of getting corrupted downloads. Especially when it seems like your update crashes and you have to restart all over again.
If you leave your phone plugged in and on WiFi it will automatically download the update (not install it automatically, but download it automatically), that's what that was about.
I'm not at all bothered, it's called having a dialogue, mate. Which is the point of the comment quote feature.
It just seems like odd priorities to me, I personally couldn't care less. Whatever lifts your boat.
If you want to live with the security problem described here so you can keep a game that's on you. Whatever.
The screen turns on and the logo appears that's it. Tried connecting to the computer and it wouldn't recognize. Effectively bricked.
Well I don't have my phone set up for wifi updates. So nothing gets downloaded to my phone. Just a notification that one is available. If it automatically downloaded, my storage capacity would have gone down...it didn't. And Apple would find a lawsuit for doing things on my phone that I didn't permit. ;-) Plus, Apples site clearly indicates "might download automatically". And if it did, you would get a message saying "Install Now" or "Install Later". No message like that for me, ever. Because I never do a wifi update on my phone.
And when I plug in my phone to iTunes, IF I hit "check for update" it still gives me the options "Download or Download and Install". As it shows here http://support.apple.com/kb/ht4623 I do neither until I'm ready. These days, I actually download the update from another site, and move it into the appropriate folder on my Mac. So when I hit Check For Update, all I get is an Install option. Which, again, I don't do until I'm ready.
Again, NOTHING is downloaded without my permission. Never has. You may want to check your settings.
Of course, I still stick to my theory, that Apple does send things to our devices without us knowing. I base that on past experiences, that my phone was working fine with no additional installs. Then suddenly it starts running into issues, like fast battery drains, random restarts/shutdowns, lags. And usually around the time of new updates or new versions of the iOS. Perhaps it's a way of forcing people to do updates when they don't want to. After all, the most common thing Apple asks of people who suddenly start having issues (for no apparent reason) with their phone is, "Did you update to the latest iOS? You should, it has 'fixes'". And they'll throw in "we can't help you any further if you don't have the latest version installed".
It's a documented feature: https://www.macrumors.com/2013/10/1...tic-ios-7-downloads-to-ios-6-powered-devices/
Developers? Hello?
What about developers? A lot of us have iOS 7.1 beta 5 and we have the SSL bug too? What is Apple doing for us to fix our vulnerability? There still is no beta 6
What about developers? A lot of us have iOS 7.1 beta 5 and we have the SSL bug too? What is Apple doing for us to fix our vulnerability? There still is no beta 6
Be that as it may, it's never happened on any of my devices. Before getting the 5S, I had the 4S (running 6.1.2) when iOS 7 came out. It took me a couple of months to convince myself I needed to updated. And nothing was ever downloaded automatically for me. You have to make sure you have Prevent iPods, iPhones and iPads from syncing automatically, and Sync with this iPhone over Wi-Fi unchecked. And just now, when I plugged my phone to my Mac and clicked on it in iTunes, I got the message An newer update is available [Download Only] or [Download and Install], I cancelled. I unplugged and plugged in again, and that message popped up again. Indicating that nothing was downloaded. I checked off Never Ask This Again and Cancelled it. And it never asked me again. When I unplugged and plugged in again.
That's not to say it didn't happen to anyone else, as it obviously did according to that article. Which is why I have everything set up manually. I don't even have iTunes set to check for updates. I do that manually. Just like the battery issue didn't affect everyone. Or how some of the known issues happened only to some people, not everyone.
Has anyone who has manual updates set up on their iPhone and in iTunes, noticed that iOS 7 automatically downloaded on their iPhones when it was released?
There are more and more people who don't even plug their phone into a computer at all or use iTunes, and certainly they've come across this.
But, even that aside, there might certainly be situations where people don't experience this kind of thing, perhaps they aren't on a good enough WiFi connection for long enough while their phone is also plugged in to get the download to actually happen (as that is how that feature works), or perhaps on connections that have some sort of bandwidth prioritization or even filtering that might be in place somewhere which might get in the way of this working, but those much less common circumstances aside, and perhaps some other strangeness that might happen and apply to some people (kind of like bad batteries for some while not for others), the automatic download of updates is an existing feature that isn't within the control of the user and a lot of people end up running into it.
MITM attacks can defeat SSL even without this bug if the user doesn't manually verify the certificate credentials by looking at the organizations name attributed to the certificate. This can be done using ettercap in combination with SSLstrip and other programs for such activities.
Even then a cross site scripting vulnerability in a client side app, such as the browser, which are found all the time can allow SSL credentials to be compromised via the ever so common phishing emails.
Most users don't know how to adequately protect themselves from those types of compromises so the presence of this issue doesn't really make unknowledgeable users less secure anyway.
This doesn't mean that this issue shouldn't be treated seriously but it isn't the end of the world that the media is making it out to be.
Even then a cross site scripting vulnerability in a client side app, such as the browser, which are found all the time can allow SSL credentials to be compromised via the ever so common phishing emails.
Most users don't know how to adequately protect themselves from those types of compromises so the presence of this issue doesn't really make unknowledgeable users less secure anyway.
This doesn't mean that this issue shouldn't be treated seriously but it isn't the end of the world that the media is making it out to be.
I would understand that, if the 1.3 Gig included the update... but yet it wasn't even downloaded..
This was generally.