Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Google prevents login #140

Open
Charadon opened this issue Aug 25, 2019 · 20 comments
Open

Google prevents login #140

Charadon opened this issue Aug 25, 2019 · 20 comments

Comments

@Charadon
Copy link

Charadon commented Aug 25, 2019

After putting in e-mail, google gives the following message:

You are trying to sign in from a browser or app that doesn't allow us to keep your account secure. Try using a different browser.

I'm on Debian 10 Buster

@itsyoshio
Copy link

itsyoshio commented Aug 25, 2019

+1, i'm on arch linux if that's relevant

@w3bb
Copy link

w3bb commented Aug 26, 2019

+1 Getting this on Gentoo, with and without the appimage.

@algometric
Copy link

+1, AppImage on Arch using LD_PRELOAD=/usr/lib/libnss3.so

@mikaelprag
Copy link

+1, AppImage on Mint 19.2.

@Mhowser
Copy link

Mhowser commented Aug 26, 2019

From the Discord help server image

@MCMrARM
Copy link
Member

MCMrARM commented Aug 26, 2019

oh wait actually, isn't this the wonderful recaptchav3

@MCMrARM
Copy link
Member

MCMrARM commented Aug 26, 2019

Seriously though, can we please make recaptchav3 illegal by law, I have no idea how to tackle this right now, seriously, fuck Google.

@w3bb
Copy link

w3bb commented Aug 26, 2019

Maybe open a browser for authorization? Or maybe have some way to forward the captcha?

@Mhowser
Copy link

Mhowser commented Aug 26, 2019

I'm sure recaptchaV3 must violate some GPDR laws.

@w3bb
Copy link

w3bb commented Aug 26, 2019

I'm sure it does but do they really care? They can pay the fines.

@Unkorneglosk
Copy link

Same for me on Ubuntu MATE 19.04 amd64.
I think it's this beautiful ReCaptcha dumb bot.
I do agree with @w3bb to do like Discord app: openning the users browser for authorization.

@MCMrARM
Copy link
Member

MCMrARM commented Aug 27, 2019

It's not feasible without adding a browser extension.

@Charadon
Copy link
Author

To be honest, I wouldn't mind installing a browser extension if it came down to it.

@w3bb
Copy link

w3bb commented Aug 27, 2019

As long as it works on Firefox it's better than not being able to play at all. Possibly a userscript?

@beckadamtheinventor
Copy link

+1 A friend of mine has the same issue. Built from source, if that makes a difference.

@Mhowser
Copy link

Mhowser commented Aug 28, 2019 via email

@MCMrARM
Copy link
Member

MCMrARM commented Aug 28, 2019

hmm Chrome/Chromium has that automation mode puppeter uses that I could use as well afaik. Wonder if Firefox has something similar.

It should be enough to be able to inject a script onto the webpage that would connect over a websocket back to me.

@w3bb
Copy link

w3bb commented Aug 28, 2019 via email

@MCMrARM
Copy link
Member

MCMrARM commented Aug 29, 2019

Either way, the following flow has to be done to replace the playdl-signin-ui:
0) Have the following JS available:

(function() {
    window.mm = {};
    window.mm.showView = function() {
        // Forward this to code, this means we're ready to show the login window; optional; can be removed
    };
    window.mm.setAccountIdentifier = function(identifer) {
        // Forward this to code, this is the email we need to save
    };
    window.mm.log = function(what) {
        console.log(what);
    };
  1. Open https://accounts.google.com/embedded/setup/v2/android?source=com.android.settings&xoauth_display_name=Android%20Phone&canFrp=1&canSk=1&lang=en&langCountry=en_us&hl=en-US&cc=us
  2. Once the URL has #close, the flow is finished, retrieve the following cookies: oauth_token and user_id. My code also requires the account identifier you can get by injecting the JS above.

If anyone has any ideas how to do it nicely using an existing browser, let me know.

@donmor
Copy link

donmor commented Oct 25, 2019

Either way, the following flow has to be done to replace the playdl-signin-ui:
0) Have the following JS available:

(function() {
    window.mm = {};
    window.mm.showView = function() {
        // Forward this to code, this means we're ready to show the login window; optional; can be removed
    };
    window.mm.setAccountIdentifier = function(identifer) {
        // Forward this to code, this is the email we need to save
    };
    window.mm.log = function(what) {
        console.log(what);
    };
  1. Open https://accounts.google.com/embedded/setup/v2/android?source=com.android.settings&xoauth_display_name=Android%20Phone&canFrp=1&canSk=1&lang=en&langCountry=en_us&hl=en-US&cc=us
  2. Once the URL has #close, the flow is finished, retrieve the following cookies: oauth_token and user_id. My code also requires the account identifier you can get by injecting the JS above.

If anyone has any ideas how to do it nicely using an existing browser, let me know.

I managed to get the two cookies from chromium by accessing this url.
image
I signed in here and found the two in the button at the start of the address bar. Is there any way to import them into the launcher?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants