News for hackers. Stuff that matters.
Re:Starting January 4 Google will block sign-ins from embedd... by paxys on Thursday November 19, 2020 @06:42PM (#25155767)
Quite the opposite actually. OAuth is designed to broker token exchange between two services in a standards-compliant web browser. Apps have increasingly been getting around it by embedding browser shells in their own interface, making the process less transparent for the end user. This opens users to all kinds of phishing attacks (e.g. an app might show you a Google sign-in page which is actually hosted on their own server, or steal your credentials even if you are actually on google.com, or automatically click "approve" without any user feedback etc.)

Enforcing that OAuth is handled in a browser controlled directly by the OS is the right thing to do.

Re:Starting January 4 Google will block sign-ins from embedd... by mehrdadn on Thursday November 19, 2020 @06:52PM (#25155854)
> an app might show you a Google sign-in page which is actually hosted on their own server, or steal your credentials even if you are actually on google.com

I'm confused, how does "this browser is not supported" translate into "this request is coming from a third party server"? Can't a third party just use whatever browser is supported to send the request?

Re:Starting January 4 Google will block sign-ins from embedd... by paxys on Thursday November 19, 2020 @07:14PM (#25155995)
The idea is that users should not be expected to or used to entering their Google credentials outside of a browser they don't fully trust.
Re:Starting January 4 Google will block sign-ins from embedd... by andreabedini on Friday November 20, 2020 @04:04AM (#25158662)
> entering their Google credentials outside a browser Google doesn’t fully trust

FIFY

As the user, I fully trust my Epiphany browser.