On Mon, 31 May 2010 08:58:35 -0700
Jann Gobble <[email protected]> wrote:

Some very good points, 

> Okay, I think we really need to expand on something...
> 
> oAuth was never designed to promote any app developer to bypass the
> built-in web browser (from an App) -- (ie: using UIWebView).  There
> are many reasons for this.  If one wanted to steal usernames and
> passwords, it is VERY easy to simulate the look and feel of Twitter's
> login page for oAuth in order to take the username and password of
> the person logging in. 

Quite true.

> ...  In other words, using the UIWebview is insecure 'cos the
> user does not have the built-in notifications (some would say
> guarantees -- although I don't see them as guarantees) that a
> built-in web browser offers.  That is, the UIWebView does not
> necessarily show the URL line with the REAL url that the user is
> being referred to.  I can easily put a UITextField at the top of any
> UIWebView, put the Twitter URL in that and displaying a lock symbol
> somewhere on my UIWebView.  This "looks" like the user is going to
> the right place but indeed I may be doing a man-in-the-midle type
> attack.

Indeed a standalone app can fool the user. So can a well designed web
page, it is not that hard. Fooling users is big business these days.
Web services are an excellent tool to do that. Hey, even many
legitimate web services make good money by getting users to pay for
completely useless products and services.

>...  One of the primary reasons oAuth was developed was to ensure
> that the app/website NEVER got access to the user's password

Yes that is a key point. This point makes a lot of sense for a web
based service that acts together with twitter to do something on the
user's behalf. The main risk for the user here are malicious web
services.

My point in saying a webview in the application is that it is more
secure than using a browser *from the point of view of the
application*. 

Inside of my application I can forward a URL to the
system default browser, or I can handle it myself. When forced to to
oauth, I have to do one or the other. Since I have zero information on
what the user has installed as their default browser, I have to assume
it is not secure. 

Aside from that, hopping to the browser and back is a
really ugly solution. 

As I said before, a lot of this stuff is inherently insecure for
reasons completely unrelated to oauth or xauth.

In any case Jann, you have convinced me of something I strongly
suspected - I really should get xauth for my application as well.

Be safe,

Bernd

-- 
Bernd Stramm
<[email protected]>

Reply via email to