News for hackers. Stuff that matters.
Re:Using Rowhammer bitflips to root Android phones by josephg on Monday October 24, 2016 @07:06AM (#12777866)
Because the trust model on phones is different.

On old UNIX mainframes the trust model had 2 kinds of actors:

- System administrators

- Users

The biggest security concern was one user getting access to the files of another user on the same system. The sysadmin decided which applications to trust (and most of them were either opensource or made by big companies, so we didn't have to worry about application developers doing nasty things). As a result, applications just ran with all the permissions of the user who started them. They could do anything that the user themselves were allowed to do, like read all your files, open a network connection and send your secrets out over the internet. But so long as users didn't run any dodgy programs it was (mostly) fine.

All modern desktop operating systems inherit that system. But over the last couple decades three things have changed:

- Computers got so cheap that now everyone has their own

- There are more apps than ever, and some of them are malicious

- There aren't enough sysadmins to save grandma

Modern phones we have a much better security model, which they inherited from the web. There are two changes:

- Multiuser support is gone at an application level.

- Apps are sandboxed from one another to protect you and your data from malicious apps. The way they do that is by isolating each app on the phone so no app can read&write to any of the data owned by another app.

For example, if you use google docs then by necessity you have to trust the docs app with your documents. But thats it! The google docs app doesn't get to access to your facebook login information. And the facebook app doesn't have access to your google account. If you had equivalent native apps on your desktop, these apps would be able to read one another's files!

But rooting your phone (at least partially) ruins all that! Rooting (by definition!) gives some 3rd party apps the capacity to access data stored by other apps on your device, which ruins the phone's security model.

The reason why some manufacturers (like apple) take a hardline stance against rooting is that if rooting your phone was easy, some app developers would undoubtably decide they'll only function on rooted devices. (This happens on android today for wifi sniffers and stuff like that.) If enough apps do that, the manufacturers will feel pressure to make it easy to disable app sandboxing, which will result in more and more apps wanting "Full permissions on your phone". People will mash "yes" on the install box (nobody reads that stuff anyway) and before you know it there'll be malware on your phone reading your email and threatening to send porn to your boss on your behalf if you don't pay up. DDoS attacks will come from phones, and will cripple the mobile network. And to fix all that norton will release an android version which will start scanning your phone for viruses at the worst possible moment of that show you like on netflix.

And that is why rooting your phone is hard.

Re:Using Rowhammer bitflips to root Android phones by kps on Monday October 24, 2016 @11:09AM (#12779464)

  > […] the data owned by another app.
This makes me sad. I don't want my data owned by an app, I want it owned by me.

(This does not imply allowing all software running on my behalf access to all of my data all of the time.)

Re:Using Rowhammer bitflips to root Android phones by URSpider94 on Monday October 24, 2016 @11:52AM (#12779903)
the parent is using "owned" in the filesystem sense of the word, meaning what entity controls access and permissions for the files. That's completely separate from ownership of the data, in the sense of copyright and data portability.

Apps owning their own data in Android should make you happy, not sad, because it's what prevents a malicious app from hoovering up all of your Tinder messages, or your financial data from Mint.

Re:Using Rowhammer bitflips to root Android phones by donutz on Monday October 24, 2016 @01:16PM (#12780765)
> Apps owning their own data in Android should make you happy, not sad, because it's what prevents a malicious app from hoovering up all of your Tinder messages, or your financial data from Mint.

That's well and good, but it also prevents YOU from hoovering up all your data.

Re:Using Rowhammer bitflips to root Android phones by kps on Monday October 24, 2016 @01:13PM (#12780726)

  > That's completely separate from ownership of the data
No, it isn't. Under the app-controlled model, my access to my data is limited to what the app offers.

  > […] it's what prevents a malicious app from hoovering up all
  > of your Tinder messages, or your financial data from Mint.
That's an implementation of access control using the app-owned-data model. It's not the only possible implementation of access control.
Re:Using Rowhammer bitflips to root Android phones by Dylan16807 on Monday October 24, 2016 @05:21PM (#12783034)
> The reason why some manufacturers (like apple) take a hardline stance against rooting is that if rooting your phone was easy, some app developers would undoubtably decide they'll only function on rooted devices. (This happens on android today for wifi sniffers and stuff like that.)

Are you claiming that wifi sniffers could work without root, and require root for other reasons? An app that uses root to work around a gap in the permission system is not in support of your point.

Also, apps can already force the user to grant them very invasive permissions or exit. Yet I don't see it being universally abused.