So, after one installs iOS 7.0.6 Crucial SSL security fix on iPhone, iPad and AppleTV, then the question is whether one's other Mac devices are okay, especially the browsers.
isn't this security issue only a problem on public networks? if you are on a secure wifi or even using data, are you really at risk of this exploit?
Theoretically, yes, you're still at risk. However, it's only "easy" on public wifi. Personally, I just stayed off public wifi until I got it fixed. But I avoid public wifi anyway.
Best way is to avoid the Internet altogether. I never connect. I type all my correspondence on a typewriter and post it to my solicitor for action on a daily basis.
Typing usernames/passwords takes 2-3 days of correspondence.
So, after one installs iOS 7.0.6 Crucial SSL security fix on iPhone, iPad and AppleTV, then the question is whether one's other Mac devices are okay, especially the browsers.
It would appear not ! "Users of Apple's OS X operating system are being warned to take care when browsing online as they wait for a solution to a security flaw."
> Apple users in security warning
The SSL fix is part of OS X 10.9.2, which was already nearing release. I suspect the delay is just a matter of final bug testing on the larger update and will be released this week if not later today. Any longer and they would have issued a separate patch. If older OS versions are vulnerable, they'll likely release a patch for Snow Leopard and up at the same time (no sense in fixing the older stuff now while the current version is unpatched).
Chrome and Firefox rely on different implementations of SSL/TLS, meaning that they aren’t subject to the same vulnerability, as it’s in Apple’s code. That means that in the meantime you should be able to safely browse with them instead. Until the vulnerability is fixed, it would be best to do any secure tasks you need on an alternative browser like Chrome or Firefox, or on a patched iOS device.
has anyone had any problems with this update? a friend of mine just bricked her phone after updating...it was an iPhone 5s.
Mine "died", too. I had to go through the whole factory reset and then restore from previous backup rigmarole.
However, since it was the second time this happened, I talked to Apple and they said since the phone DID restore and is working correctly, the phone is fine (although I couldn't get them to actually check it out) and my computer/iTunes is to blame.
So I'll be uninstalling and reinstalling iTunes and crossing fingers for the next update.
For those of us stuck on older OS X versions (my Mac Pro can't be upgraded beyond Snow Leopard), I just checked that it's not an issue for at least 10.6 and older, since Apple switched from OpenSSL to their own implementation after that.
Someone posted a way to check too:
"""
you can verify that under that system Safari is using OpenSSL. To do so, simply move /usr/lib/libssl.*.dylib elsewhere and try to run Safari. It will fail due to missing libraries.
On 10.9 Safari will happily run with OpenSSL libraries removed.
"""
Note that of course, more than Safari is affected, but this may be a good way to check if your system and your software is using the OpenSSL implementation.
