Open Bug 1862395 Opened 11 months ago Updated 17 days ago

Incorrect browser version in user agent when resistFingerprinting is enabled

Categories

(SeaMonkey :: General, defect)

SeaMonkey 2.53 Branch
defect

Tracking

(seamonkey2.53? affected)

ASSIGNED
Tracking Status
seamonkey2.53 ? affected

People

(Reporter: supsm2017, Assigned: nsITobin)

References

(Blocks 1 open bug)

Details

(Whiteboard: SM2.53.20)

Attachments

(2 files, 1 obsolete file)

Steps to reproduce:

  • Enable privacy.resistFingerprinting in about:config
  • View user agent in about: or a website

Actual results:

User agent is "Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:-1.0) Gecko/20100101 Firefox/-1.0"
Version is incorrectly -1.0. Seamonkey uses a now-incorrect formula to predict the latest ESR release and is possibly getting the incorrect current version number (nsRFPService::GetSpoofedUserAgent in toolkit/components/resistfingerprinting/nsRFPService.cpp).

Expected results:

Firefox version number should be something more sensible. In firefox upstream the user agent version is pretty much hardcoded through the build system.

I'm not sure what Seamonkey is doing, but we took out the code to try to calculate the ESR version a bit ago...

Has been so for ages. Not really supported so not exposed in the ui either. I will take a look when I find some time.

Status: UNCONFIRMED → NEW
Ever confirmed: true
Duplicate of this bug: 1780833

@Sylvestre Ledru Re: bug 1780833 (duplicate)
Comments that help move issues towards a resolution (like all of this thread) are always welcome.
Comments that falsely pretend that a bug is invalid or resolved (when it is recognised to exist and persist), however, are not.

Looking at it I am /reasonably/ able to determine the -1 version is actually correct for the code as written because SeaMonkey's major version is 2 the error is using the Application version and not the platformVersion.

Looks like it was later resolved by preproccessing in a constant based on MOZILLA_UAVERSION. For SeaMonkey it would make more sense to bind it to the Firefox Compatibility Version pref as this would be more useful to users.

Assignee: nobody → tobin

Simplified with a build var

Attachment #9421719 - Attachment is obsolete: true
Blocks: 1737436

The usefulness of an actual pref to set the compatibility version even for other purposes remains unclear when site-specific user agent overrides is a noted feature thus that can be done in another bug if desired.

should be in the next 2.53.20 b1 pre for testing

Status: NEW → ASSIGNED
Whiteboard: SM2.53.20
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: