I'm pretty sure anyone charged with implementing the oauth protocol should be able to make a fairly informed judgement about what oauth does and doesn't do and the implications of that scope. Like all security, it is about layers ... And oauth isn't all layers. That's obvious.
I don't think writing about that helps the spec too much, past saying "oauth isn't a one stop shop for end to end security" sent from my android phone On Sep 6, 2011 8:28 PM, "Michael Thomas" <m...@mtcc.com> wrote: > Melinda Shore wrote: >> On 09/06/2011 11:11 AM, Jill Burrows wrote: >>> I repeat, it is not an OAuth problem. >> >> If I'm reading Mike correctly (and if I'm not it won't be the >> first time I've misunderstood him), he's not really asking for >> OAUTH to solve this particular problem but to clarify the >> documents and beef up discussions of what is and is not in >> scope. He read the document and couldn't figure out whether >> or not this particular problem is the business of the working >> group. > > I'm fairly certain that if somebody were deploying oauth for their servers > that unless the document told me that oauth doesn't provide protection > against third party snooping if it's embedded in any app, most people wouldn't > have a clue that that was a dangerous assumption. > > What this says is that oauth only works in one use case, and that only the > user can tell the difference. Given the proliferation of phone apps and > embedded webviews, it seems that the original assumptions of oauth are > no longer up to date. > > Mike > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth
_______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
