search

9b / chirp

Interface to manage and centralize Google Alert information
https://pypi.org/project/google-alerts/
MIT License
233 stars 21 forks source link

New install having issues with google captcha during account test #22

Closed jalewis closed 5 years ago

jalewis commented 5 years ago

My mongoDB became corrupt, so I had to wipe the DB, which wiped all connection info. Adding my google account to the GUI errors that there is a captcha and authenticating via the browser does not allow me to get around the captcha.

The google-alerts CLI works as expected and pulls info with no issues. This appears to be unique to the chirp GUI.

"Authentication Failed! Google is forcing a CAPTCHA. To get around this issue, authenticate within your web browser, pass the CAPTCHA and try to run this script again. Once authenticated, this module will cache your session and load that in the future"

9b commented 5 years ago

Is the version of Google alerts updated within the path of chirp?

On Fri, Nov 23, 2018 at 2:36 PM Jason Lewis notifications@github.com wrote:

My mongoDB became corrupt, so I had to wipe the DB, which wiped all connection info. Adding my google account to the GUI errors that there is a captcha and authenticating via the browser does not allow me to get around the captcha.

The google-alerts CLI works as expected and pulls info with no issues. This appears to be unique to the chirp GUI.

"Authentication Failed! Google is forcing a CAPTCHA. To get around this issue, authenticate within your web browser, pass the CAPTCHA and try to run this script again. Once authenticated, this module will cache your session and load that in the future"

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/9b/chirp/issues/22, or mute the thread https://github.com/notifications/unsubscribe-auth/AAe21ZwvukAIa3neruvjw4fmhM-bJkLUks5uyE4kgaJpZM4YxEHc .

-- Still tracking threats without PassiveTotal? Save time, boost your analysis. Register for free https://www.passivetotal.org/register!

jalewis commented 5 years ago

Yes.

9b commented 5 years ago

That specific error comes from the google-alerts library and is not included in the latest version of the library. It's since been updated to reflect the new seed process that allows for authenticating via the Chromium browser and auto-extracting the cookie.

I suspect that your configuration file may be empty or old or the local version of google-alerts from the Chirp requirements is out of date. If you're not using venv, consider doing so and double-checking the version of the module. If you activate the venv, you should be able to perform an update.

jalewis commented 5 years ago

(venv3) jlewis@osint:~/chirp$ pip install google-alerts --upgrade Requirement already up-to-date: google-alerts in /home/jlewis/venv3/lib/python3.5/site-packages (0.2.0) Requirement already satisfied, skipping upgrade: requests in /home/jlewis/venv3/lib/python3.5/site-packages (from google-alerts) (2.18.4) Requirement already satisfied, skipping upgrade: beautifulsoup4 in /home/jlewis/venv3/lib/python3.5/site-packages (from google-alerts) (4.6.0) Requirement already satisfied, skipping upgrade: certifi>=2017.4.17 in /home/jlewis/venv3/lib/python3.5/site-packages (from requests->google-alerts) (2018.1.18) Requirement already satisfied, skipping upgrade: chardet<3.1.0,>=3.0.2 in /home/jlewis/venv3/lib/python3.5/site-packages (from requests->google-alerts) (3.0.4) Requirement already satisfied, skipping upgrade: idna<2.7,>=2.5 in /home/jlewis/venv3/lib/python3.5/site-packages (from requests->google-alerts) (2.6) Requirement already satisfied, skipping upgrade: urllib3<1.23,>=1.21.1 in /home/jlewis/venv3/lib/python3.5/site-packages (from requests->google-alerts) (1.22)

I did notice that requirements.txt has this "google-alerts==0.1.6"

jalewis commented 5 years ago

So i wiped everything again and now things are working... IDK what was borked, but seems ok now.