sprockkets

Hmm...maybe the reason why Intel failed is because there is no compelling advantage to using atom chips vs any arm chips, not the Apple A series. No one considers them high end. Android didn't fail to help Intel, but Intel failed to take over the market by force. Kinda hard to profit from those chips when you priced them to dump on the market and they weren't great performers for battery life.
 Only DED could frame this as an apple vs everyone else. So predictable.

 "As noted yesterday by PC World, the cancelation of phone-scaled Atom chips by Intel also "casts a dark shadow over the rumored Surface Phone," a vaporware product that imagined packing a desktop PC into a smartphone, which could then be plugged into a monitor and keyboard using Microsoft's "Continuum" strategy to run legacy x86 software."

 Microsoft was NEVER going to release a phone compatible with the ancient win32 programs. That would be stupid and violate every security feature WM10 has.

It isn't hard to do this. Just set it to be encrypted based off a passphrase you invent.

Problem is....

People choose bad passphrases, which can be easily brute forced offline since apple will still give them the data. People forget them. And if they forget, you lose - everything.

Of course, one could forget the password but still have their iphone. Remake the password and resync. If you lose your device though, you are screwed if you forgot your "key."

Might blow some peoples minds here but Google already does this with Chrome Sync and Mozilla with their sync. They can't read your browser history you sync with them if you pick a passphrase/password. Even if that password is the same as your main account, using it still doesn't grant them access.

rhinotuff said:

I commented on this yesterday about DED reaching too far on his articles, but for some reason it was removed?

Get used to it. Daniel aka corrections does that, and only for his articles as well.

Oh noes! Android Nexus devices don't even use this feature in the kernel! Damn, don't even need a patch! In fact Google's guidelines said to not even compile the feature into the kernel as they don't need it! No, even if you get a reply from /proc/keys, it still isn't used. So the vast majority of devices, don't even use it and are not vulnerable by default.

Oh wait, even older devices don't even use the affected kernel! And for those that do run 5.0 or up and SELinux stops it!

And it gets better! It takes a core i7 up to 30 minutes just to even exploit the bug! It's not even instant!

What will Daniel do when all the information in his flame bait article turn out false again? Nothing, because he doesn't give a shit. Just like he will never fix his article about how an Android exec admitted android didn't focus on security, and was an error in translation that his source fixed, but he didn't. Thanks to him melgross keeps posting about it on ars. 

You know Dan, if you put the same effort into researching for others that you do when something negative comes around for apple, you wouldn't have posted this. But that's being "fair and balanced", which you obviously aren't.

Thanks Dan, the Rush Limbaugh of the tech world!