CloudFlare Working On New System That Removes CAPTCHAs For Tor Users (softpedia.com)
Tor users have long criticized CloudFlare for annoying CAPTCHAs, but it appears the CDN provider is finally working on a fix. An anonymous reader writes: CloudFlare is working on a new system called "Challenge Bypass Specification," which it wants to deploy as a Tor Browser extension and replace the CAPTCHAs Tor users see when trying to access a website protected by CloudFlare. This new system will have users solve one CAPTCHA at the beginning and after that, the browser extension will use nonces (one-time authentication tokens) to prove the user's real identity before accessing a CloudFlare-protected site.
One time token per Tor user.... doesn't that mean it identifies the user??? Sounds anti-Tor.
So in the end ... you can easily track Tor users ...
Oh, and this doesn't do jack shit to stop bots ... a user can authenticate one bot manually by viewing the captcha ... then letting it run for hours, so theres a startup cost, but after that ... its back to bot town.
And how do you get users to do captchas for you? Something like the URL in my sig, which uses a 'game' to get users to do actual work no wants to pay for.
Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
If nothing else, this is just another confirmation that the modern web isn't set up to allow you to be anonymous.
That's a problem we techy types should be fixing, not encouraging solutions that identify the user even more.
, the browser extension will use nonces (one-time authentication tokens)
Couldn't they have come up with a better name one that doesn't evoke "Kiddy Fiddler"
Build a Man a Fire, and He'll Be Warm for a Day. Set a Man on Fire, and He'll Be Warm for the Rest of His Life.
The problem here is that the TOR browser does one separate circuit per domain. So if you visit site A through TOR and have to solve a captcha because of cloudflare, and then visit site B, your IP will be different, and you'll have to solve a captcha again. AFAIK this problem only surfaced (doing captchas for every cloudflare site) when TOR adopted that behaviour. Before, everything was routed through one circuit, and you only had to fill in one captcha.
Read subject of comment ^^
I'm guilty of not reading the article. I don't have to because in the summary I see "a Tor Browser extension" and stopped.
What the eff? That completely defeats the purpose of having something that's not "trackable". It could very well be an extension that phones home the activity of the user to a government entity so they can catch more of the REALLY bad guys - that being whatever's on the menu of good catch this week/month/whatever. If it were open source, it's still BS because you KNOW most people that use Tor aren't developers and aren't going to set up an environment to compile an extension to ensure every line of it is clean. Let alone what it sends to CAPTCHA to work around the problem; doing so can be used to easily identify who is using Tor to make them a target rather than the exit nodes or whatever they're called now.
https://en.wikipedia.org/wiki/Nonce_(slang)
Figures. They are all child porn browsing nonces on tor anyway.
Yeah, let's turn Tor Browser into swiss cheese by adding plug-ins from all sorts of characters. Fuck that and fuck CloudFlare.
And fuck you archive.is for once being a very usable site to now showing up as CloudFlare shit.
I guess once you become popular enough, you decide to alienate your users.
here's a plug to keep it open for us so you don't have to use hands.
I'm not especially inclined to bother with a site when Cloudflare shoves a captcha in my face not just to create and account or make a post; but to view its front page in the first place. My "One more step" is nearly always my browser's "back" button. Cloudflare can take their precious snowflake of a half-assed CDN and bite my shiny daffodil ass.
Imagine all the people...