this post was submitted on 08 Jan 2024
164 points (97.1% liked)

Privacy

32173 readers
806 users here now

A place to discuss privacy and freedom in the digital world.

Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.

In this community everyone is welcome to post links and discuss topics related to privacy.

Some Rules

Related communities

much thanks to @gary_host_laptop for the logo design :)

founded 5 years ago
MODERATORS
 

Today, I noticed that Google wasn't loading on Mull (Firefox Fork). Switching useragent with the extension Chameleon makes the page load again.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 13 points 11 months ago (2 children)

Yep, with Mull 121.0.0 i got a blank page.

[–] [email protected] 8 points 11 months ago

Confirming: me too

[–] mo_ztt 5 points 11 months ago (1 children)
[–] [email protected] 8 points 11 months ago (1 children)

Nothing special, Mozilla/5.0 (Android 10; Mobile; rv:121.0) Gecko/121.0 Firefox/121.0. I checked the network tab, they literally return nothing.

[–] mo_ztt 13 points 11 months ago* (last edited 11 months ago) (2 children)

Mozilla/5.0 (Android 10; Mobile; rv:121.0) Gecko/121.0 Firefox/121.0.

I just did a bunch of testing. The issue is that final version number, "Firefox/121.0". Google returns very different versions of the page based on what browser you claim to be, and if you're on mobile Firefox, it gives you different mobile versions depending on your version:

% wget -O - -nv -U 'Mozilla/5.0 (Android 10; Mobile; rv:62.0) Gecko/121.0 Firefox/41.0' https://www.google.com/ | wc -c
2024-01-08 15:54:29 URL:https://www.google.com/ [1985] -> "-" [1]
    1985
% wget -O - -nv -U 'Mozilla/5.0 (Android 10; Mobile; rv:62.0) Gecko/121.0 Firefox/62.0' https://www.google.com/ | wc -c
2024-01-08 15:54:36 URL:https://www.google.com/ [211455] -> "-" [1]
  211455
% wget -O - -nv -U 'Mozilla/5.0 (Android 10; Mobile; rv:62.0) Gecko/121.0 Firefox/80.0' https://www.google.com/ | wc -c
2024-01-08 15:52:24 URL:https://www.google.com/ [15] -> "-" [1]
      15
% wget -O - -nv -U 'Mozilla/5.0 (Android 10; Mobile; rv:62.0) Gecko/121.0 Firefox/121.0' https://www.google.com/ | wc -c
2024-01-08 15:52:04 URL:https://www.google.com/ [15] -> "-" [1]
      15

If you're an early version of Firefox, it gives you a simple page. If you're a later version of Firefox, it gives you a lot more complete version of the page. If you're claiming to be a specific version of mobile Firefox, but the version you're claiming (edit: oopsie ~~doesn't exist or even really make sense~~ didn't exist when they set this logic up or something), it gets confused and gives you nothing. You could argue that it should default to some sensible mobile version in this case, and they should definitely fix it, but it seems to me like it's clearly not malicious.

Edit: Wait, I am wrong. I didn't realize Firefox's version numbers went up so high. It looks like the cutoff for where the blank pages start coming is at version 65, which is like 2012 era, so not real old at all. I still maintain that it's probably accidental but it looks like it affects basically all modern mobile Firefoxes, yes.

[–] [email protected] 14 points 11 months ago

Given that it's like third accidental bug in google services that affects only Firefox in the last month I hear about, I'm starting to get suspicious.

[–] VicentAdultman 2 points 11 months ago

Thanks for the tests. They make the information more reliable since I had extensions turned on.