this post was submitted on 27 May 2026
87 points (97.8% liked)

Privacy

5701 readers
204 users here now

Welcome! This is a community for all those who are interested in protecting their privacy.

Rules

PS: Don't be a smartass and try to game the system, we'll know if you're breaking the rules when we see it!

  1. Be civil and no prejudice
  2. Don't promote big-tech software
  3. No apathy and defeatism for privacy (i.e. "They already have my data, why bother?")
  4. No reposting of news that was already posted
  5. No crypto, blockchain, NFTs
  6. No Xitter links (if absolutely necessary, use xcancel)

Related communities:

Some of these are only vaguely related, but great communities.

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] sp3ctr4l@lemmy.dbzer0.com 28 points 16 hours ago* (last edited 16 hours ago) (3 children)

canvasblocker ublockorigin privacybadger

about:config ->

-> javascript.options.shared_memory = FALSE

-> privacy.firstparty.isolate = TRUE

-> privacy.partition.network_state = TRUE

-> privacy.partition.network_state.oscp_cache= TRUE

-> privacy.partition.network_state.oscp_cache.pbmode = TRUE

-> privacy.partition.serviceWorkers = TRUE

-> privacy.reduceTimerPrecision = TRUE

-> privacy.resistFingerprinting.reduceTimerPrecision.jitter = TRUE

-> privacy.resistFingerprinting.reduceTimerPrecision.microseconds = 1000 ... or... more?

... might do something to stymie this?

From the paper:

We assume default configurations for the operating system and browser.

Well I have no idea what the 'default configuration' of ... Linux ... is...

But uh, theoretically this is something you could harden against by going balls to the wall with security preferences and options in firefox, waterfox, librewolf, ironfox, something like that... maybe?

Also, its maybe possible that using a seperate container for each seperate tab could also stymie this.

[–] flambonkscious@sh.itjust.works 3 points 9 hours ago (1 children)

Interesting ideas in here, particularly the timer precision

[–] sp3ctr4l@lemmy.dbzer0.com 5 points 4 hours ago* (last edited 4 hours ago) (1 children)

Waterfox seems to already have a default of 1000 microseconds, if... I think, you go with 'strict' privacy settings option?

So on the one hand, a very brief perusal of the paper shows that the method needs like, sub 200 timings to work well.

On the other hand... I have no idea if the exploit method effectively circumvents the way this timing speed limit actually works.

I basically just sped read everything lol.

[–] wyldrstallyns@lemmy.dbzer0.com 1 points 3 hours ago

So, you're saying you only needed one timer?

[–] alapakala@quokk.au 11 points 13 hours ago (1 children)

OPFS

oh you firefox

Seems like a feature vendors need reconsider unimplementing/threat remodeling.

[–] sp3ctr4l@lemmy.dbzer0.com 4 points 5 hours ago

Yeah I apparently missed all this but yeah, there seems to have been a significant hubub of basically... wait why do we even need this at all?

To satisfy lazy corporate web devs who can't be bothered to use existing APIs properly?

That's basically my take after after a light review of reading several threads in various places around this, over the last few years.

[–] far_university1990@reddthat.com 2 points 11 hours ago (1 children)

Mullvad browser maybe better for this than librewolf?

[–] sp3ctr4l@lemmy.dbzer0.com 2 points 5 hours ago (1 children)

Potentially?

Maybe?

I would not call myself an expert here, I don't... dev webbrowsers, more like I'm a privacy minded power user.

I'm literally just spitballing, I can guarantee nothing.

Maybe if I did a full crash course over like a month or two, I could have what I would call a 'semi-informed' opinion.

[–] far_university1990@reddthat.com 1 points 4 hours ago

Because mullvad based on torbrowser which known very fingerprint resistant.