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

NoCaptcha #68

Open
0xbzho opened this issue Oct 26, 2016 · 4 comments
Open

NoCaptcha #68

0xbzho opened this issue Oct 26, 2016 · 4 comments

Comments

@0xbzho
Copy link

0xbzho commented Oct 26, 2016

New hosters are increasingly using NoCaptcha, and existing hosters using ReCaptcha are advised to upgrade. Any work being done on support for these captchas? I'm prototyping using --captchaprogram with the extra variables been passed by Plowdown as environment variables. (For instance, this is how Anti-Captcha works with NoCaptcha: https://anticaptcha.atlassian.net/wiki/display/API/Documentation+in+English).

@mcrapet
Copy link
Owner

mcrapet commented Oct 26, 2016

Hi,

--9kweu=KEY                  9kw.eu captcha (API) key
--antigate=KEY               Antigate.com captcha key
--captchabhood=USER:PASSWD   CaptchaBrotherhood account
--captchacoin=KEY            captchacoin.com API key
--deathbycaptcha=USER:PASSWD DeathByCaptcha account

Don't know if CaptchaBrotherhood is working; captchacoin seems dead.

So you would like support for:
https://anti-captcha.com/

@0xbzho
Copy link
Author

0xbzho commented Oct 26, 2016

Kind of. Anti-Captcha supports the antigate API so it already works with plowdown for image-based captchas. The issue is more that the additional complexity of NoCaptcha means the idea of Captcha solvers merely needing an image file---as the --captchaprogram assumes---is no longer viable. At the minimum they need the site URL and the site's public key but ideally they need details of a user-supplied proxy in case Google requires the captcha to be solved from the same IP the page is requested by, the original cookies, the useragent, etc. My thinking was rather than complicate the Captcha code in core.sh any more we could just delegate to a user-supplied binary.

@mcrapet
Copy link
Owner

mcrapet commented Oct 26, 2016

--captchaprogram arguments should be improved indeed.
We are missing 3 arguments: websiteUrl, websiteKey, userAgent.

The temporary proxy could be setup in the captchaprogram.

captcha_process (module) API is not adapted, because it takes an image (local or remote).
nocaptcha_captcha_process API should be added in core.sh (likesolvemedia_captcha_process for example). But solvemedia_captcha_process invokes captcha_process... here is the problem.

This is tricky..considering architecture point of view.

Do you know an hoster site using this new NoCaptcha ? (I think this name is confusing and stupid)

[EDIT] Dont know if I have been clear enough, I speak about Anti-Captcha v2 support not v1 (which is "old school" like antigate).

@thenewcoderintheworld
Copy link

thenewcoderintheworld commented Jan 10, 2020

CBH is gone and unavailable.

Is 9kweu for both image and nocaptcha (e.g. recaptcha v2+v3) ?
https://www.9kw.eu/api.html
https://www.9kw.eu/hilfe_more.html (recaptcha instruction, post+get requests thinkable)

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

3 participants