ungoogled-chromium: Infinite Cloudflare verification loop
OS/Platform
NixOS
Installed
OS/Platform’s package manager
Version
133.0.6943.141 (Official Build, ungoogled-chromium) (64-bit)
Have you tested that this is not an upstream issue or an issue with your configuration?
- I have tried reproducing this issue in Chrome and it could not be reproduced there
- I have tried reproducing this issue in vanilla Chromium and it could not be reproduced there
Description
“Verify you are human” page keeps looping
How to Reproduce?
- Clean install browser
- Allow third-party cookies everywhere
- Attempt to open ryuugames.com (nsfw)
Actual behaviour
Verification circle continues to rotate, then new “Verify you are human” element appears
Expected behaviour
Pass Cloudflare checks, like in vanilla Chromium 133.0.6943.141 (Official Build) (64-bit) The console log seems to be the same in all browsers, yet ungoogled variant stuck on the verification page for whatever reason.
Relevant log output
Additional context
No response
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 17
- Comments: 24 (16 by maintainers)
I have the same issue after updating to 133.0.6943.141. After trying out the solution in #3012 to fix YouTube, disabling WebGL (
chrome://flags/#disable-webgl) also fixes Cloudflare verification. Is this also related to the spoofed WebGL device?Can confirm that this setting fixed the cloudflare loop issue I was having on 2 different devices, if that helps.
The changes in the PR for 134 make this opt-in, so once that lands webgl will return the same strings as vanilla chromium until the flag is set. We can update the string that flag uses at any time once we can figure out the best route.
ugh. yep, I can reproduce this as well, so it’s probably this string. I’m going to try and see if it’s triggered just by this one specifically or by anything that is non-empty
Also, it looks like swiftshader is getting deprecated so we won’t be able to use
ANGLE (Google, Vulkan 1.3.0 (SwiftShader Device (Subzero) (0x0000C0DE)), SwiftShader driver-5.0.0)without sticking out like a sore thumb in a few months.https://chromestatus.com/feature/5166674414927872
Yes, it should, so long as you don’t enable the new flag.
Weird! I’m surprised that they don’t seem to care about that. It might be a good option if we can’t figure out a better string to use.
@Ahrotahn A single space works for me for both YouTube and Turnstile.
I tested the top ~10 strings from this list and it looks like every single one of them works, except the ones with the
Google Inc. (Google)vendor (although the results might be biased because I’m using a Mac desktop); it seems like Turnstile just really dislikes the generic ones with the Google vendor.(for example, even
Google Inc. (Intel),ANGLE (Intel, Intel(R) Iris(R) Xe Graphics (0x00009A49) Direct3D11 vs_5_0 ps_5_0, D3D11)worked for me on an apple silicon macbook)I can reproduce this as a regression introduced in https://github.com/ungoogled-software/ungoogled-chromium/commit/3c764bfc0bddd5897724e2c93e87c8d68420858f (by building with https://github.com/networkException/ungoogled-chromium/commit/8bd564f8687401b1966f2f83fdb9b15e532f070c)
CC @dumbmoron
Is it reasonable to change the string in an upcoming release and make it opt-out?
Same for me on Arch, which makes debugging this a pain. I’m inclined to agree that there may be other variables involved, which has me worried that using a different string might only cause problems for a different subset of users.
@networkException @dumbmoron Since you are able to reproduce the problem, if you get the chance to do so, try a build with just an empty space for the string:
" ". Cloudflare was fine with the empty string from before and youtube just needs something. Both sites work for me with that change but so does basically everything I’ve tried except for an actual null value.When turning off graphics acceleration on my device, it just completely disables WebGL (which also fixes the issue, but not for the right reason)
It makes even more sense to be able to configure the value 😃
It shouldn’t, because it falls back to software implementation (swiftshader?) at least on Windows.
Both the blank string and the generic google vendor string works fine for me on Windows. The google vendor string is also the value returned if you have hardware acceleration disabled, so it should be a “safe” value to return. Have you guys tested with hardware acceleration disabled? My guess is that the fingerprinting is picking up inconsistencies between the vendor string and other webgl attributes (see: https://browserleaks.com/webgl), and flagging you for that. The spoofing we do only hides the vendor string but not anything else, so it’s pretty detectable.