14
Tracking users with favicons, even in incognito mode (github.com)
submitted 11 months ago by to c/privacy@programming.dev
3 comments fedilink hide all child comments

all 3 comments

sorted by: hot top controversial new old
[–] 22 points 11 months ago (1 child)

Ah, this one is an old github post. Firefox version 86 is mentioned in the table.

Back then Firefox wasn't vulnerable due to a bug that caused the browser to always grab a new favicon even if it was cached.
Nowadays the Total Cookie Protection ensures that the websites are isolated and the favicon tracking fails.

  • permalink
  • fedilink
  • source
  • hideshow 1 child comment
    •
    • [–] 3 points 11 months ago

    2 years out of date

  • permalink
  • fedilink
  • source
    •
    3 comments in c/privacy@lemmy.ml view that post
    [–] 40 points 11 months ago (2 children)

    Note that this is an issue from 2021. Firefox has implemented countermeasures since version 85, Chrome seems to have done the same.

    So while this is definitely interesting, it shouldn‘t be an issue anymore.

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] 5 points 11 months ago* (last edited 11 months ago) (1 child)

    Yep. I just confirmed it.. restarting Firefox seems to make the ID in https://demo.supercookie.me/ change. Thought as long as you keep Firefox session open the id will be the same.

    I'm not sure if the links you reference are the whole story though, because they are talking about partitioning the cache per top-level domain, which I would expect wouldn't have been enough, since the demo is specific to its top-level domain and it's not necessarily about cross-domain id.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •