News for hackers. Stuff that matters.
Re:Grammarly's OAuth Mistakes by nullindividual on Friday October 27, 2023 @11:37AM (#38039940)
The complexities of OAuth make me want to go solve an NTLM double-hop problem with a three headed dog.

Why are we seeing so many implementation mistakes? Is OAuth simply too difficult?

Re:Grammarly's OAuth Mistakes by mooreds on Friday October 27, 2023 @11:50AM (#38040108)
I think it's because

* it's a framework for authorization, with at least 8 different ways of using it (https://fusionauth.io/docs/v1/tech/core-concepts/modes has more)

* authentication is not most folks core competency

Re:Grammarly's OAuth Mistakes by belter on Friday October 27, 2023 @12:29PM (#38040603)
According to the lead author and editor of OAuth 2.0, ( who asked that is name be removed from the spec) is: "a bad protocol."

Developer Quits OAuth 2.0 Spec, Calls It 'a Bad Protocol' - https://www.wired.com/2012/07/developer-quits-oauth-2-0-spec...

"OAuth 2.0 and the Road to Hell" - https://news.ycombinator.com/item?id=4294959

Re:Grammarly's OAuth Mistakes by peter_l_downs on Friday October 27, 2023 @01:42PM (#38041532)
Strongly recommend reading this, as well as looking up Homakov's exploits. My opinion is that OAuth 2.0 is a very bad spec because in practice people do not implement it correctly. As to why? Maybe it's that the spec is split across multiple RFCs, and defines many insecure behaviors as compliant, and authorization is just hard.

When Facebook, Twitter, Github, etc. all got burned at various points in time with their OAuth implementations, you have to start looking for the common denominator.

Re:Grammarly's OAuth Mistakes by lylejantzi3rd on Friday October 27, 2023 @03:07PM (#38042591)
> My opinion is that OAuth 2.0 is a very bad spec because in practice people do not implement it correctly.

Can we just stop using oauth entirely, then? There's got to be something better.

Re:Grammarly's OAuth Mistakes by paulddraper on Friday October 27, 2023 @05:17PM (#38044085)
Oauth 2.1

> Keep in mind that when OAuth 2.0 was published in 2012, the iPhone 5 was brand new, the latest browser from Microsoft was Internet Explorer 9, single-page apps were called “AJAX apps”, and CORS was not yet an established W3C standard.

Re:Grammarly's OAuth Mistakes by dwaite on Friday October 27, 2023 @02:05PM (#38041840)
A big part is bespoke authentication on top of OAuth, rather than correctly implementing an actual standard to do such (OpenID Connect). OAuth is not an authentication protocol, it only gives guidance for delegated authorization.

OpenID Connect gives a mandated list of steps for verification.

Facebook Connect really only is supported via usage by an official SDK. If you are using an implementation that reverse engineered support for Facebook Connect rather than using the official SDK, you are on your own.

Re:Grammarly's OAuth Mistakes by az09mugen on Sunday October 29, 2023 @05:13AM (#38056900)
It's funnier when you know microsoft will abandon ntlm https://www.bleepingcomputer.com/news/security/microsoft-pla...