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

Tokens are often rejected #7

Open
antiprime opened this issue Apr 5, 2019 · 0 comments
Open

Tokens are often rejected #7

antiprime opened this issue Apr 5, 2019 · 0 comments

Comments

@antiprime
Copy link
Collaborator

Even when all challenges are completed and a token is obtained, the token is often rejected when used. Sometimes, continuing to complete CAPTCHAs will eventually result in an accepted token, but I've also completed dozens in a row without any success.

The token rejection appears to be due to the fact that librecaptcha doesn't send any of the BotGuard codes that the proprietary reCAPTCHA client does. The proprietary client actually works without BotGuard, too—if you block requests to https://www.google.com/js/bg/*, the client simply won't send any BotGuard codes, much like librecaptcha—but even the proprietary client in this configuration suffers from token rejection issues.

There are a few request parameters that the proprietary client without BotGuard sends and librecaptcha doesn't, but if even the proprietary client suffers from token rejection, the culprit is almost certainly BotGuard.

Thus, reverse-engineering BotGuard may be the only way forward. A substantial amount of work has already been done, but for a much older version of BotGuard.

Any help with this effort would be much appreciated.

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

1 participant