Although I couldn't read the present string (because it was in what appeared to be Polish), I can confirm that I can successfully access <https://www.ietf.org/> through Tor after completing the captcah without JavaScript. It worked without any problems (except the language bit but that doesn't really count). Regards, Tom Thorogood. On 17/09/14 17:44, Rhys Smith wrote: > On 17 Sep 2014, at 08:41, Leif Johansson <leifj@xxxxxx> wrote: > >> Its a ToR thing. You get hit by captchas when you aproach from a ToR >> exit node. >> >> I think ToR users are fine with that (generally speaking). >> >> I don't understand why you need JS for presenting a basic captcha. For >> instance recaptcha doesn't need plugins: >> https://developers.google.com/recaptcha/docs/display > > Well, it looks like maybe it’s *supposed* to work without JS - if you have JS disabled it presents the captcha in a slightly different way (saying "To make this process easier in the future, we recommend you enable Javascript.”), and then if you answer correctly it gives you a 186 character string to copy then paste into a second text box. When you do that, what happens with me in the Tor Browser is instead of letting you get to the site, it just starts the whole captcha process off again from scratch. > > A bug in CloudFlare’s stuff? > > Rhys. > -- > Dr Rhys Smith > Identity, Access, and Middleware Specialist > Cardiff University & Janet, the UK's research and education network > > email: smith@xxxxxxxxxxxxx / rhys.smith@xxxxxx > GPG: 0x4638C985 >