Title: It appears that Cloudflare&#x27;s Turnstile captcha product has decided Linux users are no longer considered &quot;human&quot; and therefore locked out of websites using this product.<p>While the usual explanation is that there may be a compromised device on the network, I can pass these challenges myself using my Mac, but not on Linux on the very same network. This is from a residential ISP in India, and as you can see in the screen recording, I&#x27;m using an incognito window with all extensions disabled, so it&#x27;s unlikely that the IP address or the browser configuration are at fault here.<p>* Mac: https:&#x2F;&#x2F;drive.google.com&#x2F;file&#x2F;d&#x2F;1glfS_9OkV5mw5ysU3ASZCwR5c5eCeRT3&#x2F;view?usp=sharing<p>* Linux: https:&#x2F;&#x2F;drive.google.com&#x2F;file&#x2F;d&#x2F;1WnNRUlikqfmqdELfcohu7SBfjJr9aNzZ&#x2F;view?usp=sharing<p>At a societal level, it is scary how things seem to resemble RMS&#x27; &quot;Right To Read&quot; with one corporation deciding to unilaterally deciding what browser should have access, as I&#x27;ve said elsewhere.<p>At a technical level, I speculate the issues are because Cloudflare is unable to properly distinguish between headless and regular Chrome because of changes in Chromium[1] as well as because of TLS ClientHello permutations[2].<p>[1] https:&#x2F;&#x2F;antoinevastel.com&#x2F;bot%20detection&#x2F;2023&#x2F;02&#x2F;19&#x2F;new-headless-chrome.html<p>[2] https:&#x2F;&#x2F;www.fastly.com&#x2F;blog&#x2F;a-first-look-at-chromes-tls-clienthello-permutation-in-the-wild
Upvote: