The old ATV 4 also apparently remains unpatched. For the Watch it's the other way around: only series 1 and 2 get the patch, the latest series 3 apparently doesn't. Very strange. This needs some clarification from Apple.
Those are just basic things that get updated, like there are security fixes, and realistically those come from the Unicode Consortium, so any "issues" with that would really be for them.
Not that's actual meaningful feedback that hopefully can be sent to Apple so that hopefully it's seen and given some consideration.Even for those who enjoy Emojis, it seems they are putting in way too many, so you have to search endlessly.
Apple's implementation isn't great since the scrolling isn't limited to that section, and the "Recently Used" is different depending on where you are (ie. in Messages.app vs using quick reply), and no way to pin favorites.
They should also consider grouping similar Emojis to reduce the endless list of them.
Still no apple pay on messages or messages in iCloud. The only two features I wanted. Apple is ****ing up so much this year.
Yep apparently in the older devices iOS WPA2 implementation was not correctly done and as a side benefit are not vulnerable to KRACK. According to Steve Gibson of Security Now, iOS was not vulnerable to KRACK because they misimplemented the WPA2 specification. My guess is iP7 and up is when WPA2 was fixed and therefore now those devices need the patch! Perhaps Apple will relay this information soon to clear it up for all. That could mean the non iOS11 compatible devices are all fine as well.Based on that (I could not visit the reddit link, it's blocked by my office network politics), isn't it possible that the vulnerability itself was only present in the WPA2 implementation in iOS specific versions for the mentioned models, and not for the rest of them? Thus the specific mention of those models?
So, in iOS 11.1, the "correct" (and patched) implementation is distributed to all releases?
I hope what I wrote makes sense..
As am I. I do not want 11... but I do want the KRACK fix. Why can't Apple release the fix as a stand-alone for older versions of iOS? They did it for Sierra and even El Cap without forcing an upgrade to HS.
It seems perhaps only the iP7 and up are affected. Several posts here with more info.As am I. I do not want 11... but I do want the KRACK fix. Why can't Apple release the fix as a stand-alone for older versions of iOS? They did it for Sierra and even El Cap without forcing an upgrade to HS.
Not sure you are saying that correctly. Older devices may not be vulnerable due to the WPA2 implementation in their wifi chips but newer devices are and the only iOS version that is patched for newer devices that are vulnerable is 11.1. So iP7 and and up according to the Apple security document.As has been said everywhere, KRACK is not really a problem for recent iOS versions.
But there are many other critical security fixes in iOS 11 and 11.1. Staying on iOS 10 and worrying about KRACK is really irrational, even if you were vulnerable to KRACK.
It's not really Apple's problem as mich as it seems to be some sort of a perceived/imagined problem for some people it would seem.Peoples problem with Apple listing Emoji first - it’s purely a marketing thing. It’s not either they fix the OS OR add emojis. They need hardly any, if any, resources to add Emoji whereas they have plenty of people working on building and fixing the OS. The marketing department just know people (not us on this forum) will generally be more attracted to Emoji news than bug fix lists.
And the OS is running very nicely. It’s only been a month or so but it’s nice to have a useable phone again!
Interesting you may be onto something. I suspect you were kidding but.......... See last comment here. Perhaps only iP7 and up are not "faulty" as far as the spec goes thus requires the patch.
tsdguy 0 points 12 days ago
iOS is not actually vulnerable to the major aspect of KRACK - rebroadcast of key since iOS's WPA2 implementation is faulty compared to the vulnerable official implementation.