News for hackers. Stuff that matters.
Re:OAuth Will Murder Your Children by marshray on Tuesday January 25, 2011 @02:18PM (#2140420)
Q: Why would an application developer want to make limiting promises?

A: Because more users will trust the application and be willing to authorize it.

I think this is the only correct answer. Sadly, without mechanisms in place to limit the scope of the authorization, the market is aiming for a scenario where ordinary people simply don't trust web applications. Even visiting new sites on the web for them will carry a baseline of non-specific fear.

Re:OAuth Will Murder Your Children by abhaga on Tuesday January 25, 2011 @02:44PM (#2140520)
Absolutely! It is not rare for me to get to the allow screen, notice that the app is basically requesting full access to my account which it clearly doesn't need, and leave.

As the worms spreading through e-mail show, social filtering may not be sufficient to identify rogue apps in time.

Re:OAuth Will Murder Your Children by generalk on Tuesday January 25, 2011 @02:23PM (#2140446)
Most users will never analyze the "This application requests the following permissions..." screens; see: anyone that owns an Android phone.
Re:OAuth Will Murder Your Children by marshray on Tuesday January 25, 2011 @02:40PM (#2140510)
I am not most users. Strangely, neither are most of the people I know. But we're the ones everybody looks to when they need to buy a computer, know if the web is safe, or clean up the mess when it turns out not to be.

Quit it with the "most users" reasoning, unless your goal in life is to part fools from their money.

Re:OAuth Will Murder Your Children by generalk on Tuesday January 25, 2011 @04:52PM (#2141073)
Quit it with the "most users" reasoning, unless your goal in life is to part fools from their money.

I don't follow your reasoning, but still:

Listing granular permissions is like throwing up a confirmation dialog before a destructive action: better than nothing, but more often than not gets ignored.

Yes, after that, your friends call wondering why all their data was deleted or why some app is updating their facebook wall. And you tell them to pay attention next time, and they swear they will.

And they don't.

I don't have a better solution, but that doesn't mean that this is the right one.

Re:OAuth Will Murder Your Children by brown9-2 on Tuesday January 25, 2011 @05:34PM (#2141238)
It doesn't matter if "most users" don't care about this level of information as long as they still click "allow", but it does make difference to the minority that do care. So what's the harm?

If they don't care about the information then it's presence doesn't hurt them.

Re:OAuth Will Murder Your Children by joelhaasnoot on Tuesday January 25, 2011 @03:25PM (#2140680)
The problem is lots of calls in the Android API have side-effects or can be used for a variety of reasons. Anytime you have ads for instance, you need internet access. If the app can be moved to the SD card, you need write access to that, and so on and so forth. They're little things but require opening up lots of possibilities.
Re:OAuth Will Murder Your Children by marshray on Tuesday January 25, 2011 @03:58PM (#2140829)
Yeah I don't really know about Android. The article was really more about web apps.

But granular access controls are nearly impossible to implement in practice. Unix had it right all along: a set of limited users, and root. You're doing well if you can even defend that security boundary, anything in-between tends to be root-equivalent on general purpose systems.

Re:OAuth Will Murder Your Children by shasta on Tuesday January 25, 2011 @05:03PM (#2141118)
That's ridiculous. The Unix security model doesn't even address untrusted applications, unless you think auto-downloading and running Unix executables would work out well. The situation with web security is terrible and there aren't any "good old days" we can revert back to -- every mainstream OS has done it wrong. Good security is difficult and influences many parts of a system, but if it were a priority for any of the big players, it would have already happened.
Re:OAuth Will Murder Your Children by lurker17 on Tuesday January 25, 2011 @05:47PM (#2141274)
An untrusted application is handled in running it as a dedicated user, like 'httpd' or 'nobody'.
Re:OAuth Will Murder Your Children by joesb on Tuesday January 25, 2011 @08:34PM (#2141722)
Can nobody access "user joe"'s SMS and Email?

A. If it can, then it can send my personal info to outside world. I don't care if it can't gain root access to my phone. My phone's root account is not important, my personal information inside that phone is.

B. If it cannot. Then most of my application is useless because it can't access any information at all. Why don't I add it to "trusted" zone? Because I don't trust it. And I shouldn't have to.

So what do I want? I want it to see my personal data but not being able to send it to anyone.

We're back to permission based system again.

Re:OAuth Will Murder Your Children by dpwiz on Thursday January 27, 2011 @11:21AM (#2148369)
Please educate yourself about Unix Security Contexts.
Re:OAuth Will Murder Your Children by judofyr on Tuesday January 25, 2011 @02:35PM (#2140485)
The reason is that there is no reason to analyze it. There's nothing to do on the screen, and you've already decided you want to download the app (after all, you did press the "Download" button).

Maybe 80% people will still press "Allow" instantly, but at least this makes the 20% other more comfortable.

Re:OAuth Will Murder Your Children by Janos on Thursday January 27, 2011 @07:42AM (#2147583)
We proposed a reputation mechanism for mash-ups/apps that can be plugged on OAuth. The service provider (e.g: Twitter or Facebook) records every access to the user account and sends a report after a week. Users rate the application which reputation is maintained by the service provider. Average ratings and comments are displayed when a new user is asked to grant an authorization.

Link to the paper: http://www.dundal.com/R2M-CCNC2010.pdf