Opened 17 months ago

Last modified 17 months ago

#22127 new enhancement

Think about a more elaborate defense against fingerprinting with `hardwareConcurrency`

Reported by: gk Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: tbb-fingerprinting
Cc: arthuredelstein Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

In #21675 we set dom.maxHardwareConcurrency to 1 making users uniform. The cost for those with computers with more than 1 core could be performance degradation. We could think about following a bucket approach here, too, to mitigate that while still providing fingerprinting protection: users with up to and including 3 cores report back 1 core, users with 4 and up to and including 7 cores report 4 back and users with 8 or more cores report 8 back. It would be neat if we could apply that to #18559 as well although this might be an orthogonal problem.

Child Tickets

Change History (3)

comment:1 Changed 17 months ago by tom

The cost for those with computers with more than 1 core could be performance degradation.

This will only (potentially) degrade performance for really sophisticated web applications though, right? Games that go "Oh, your PC has 4 cores so I'll spin up 3 WebWorkers to help with the ray tracing in my Canvas-based DOOM clone" or whatever. It wouldn't affect the actual browser... right?

comment:3 Changed 17 months ago by arthuredelstein

Cc: arthuredelstein added
Note: See TracTickets for help on using tickets.