News for hackers. Stuff that matters.

A comment on Cover Your Tracks. Parent comment

Re:Cover Your Tracks by spijdar on Saturday November 21, 2020 @07:52AM (#25169425)
Even with CPU rendering, there will be differences depending on the specific software libraries and system configuration, e.g. aliasing settings. Patches to one of the pieces of software doing rendering could create pixel level differences in rendered fonts that could be used to fingerprint.
[ Parent | on HN ]
Re:Cover Your Tracks by xuhu on Saturday November 21, 2020 @12:28PM (#25171080)
Still, "latest Chrome on Windows 10 and an 1080p laptop screen with Intel Graphics" should be at least ... half of the users out there ?

Yet CoverYourTracks says that even my up to date Chrome User Agent is used by one in 223 browsers, which sounds hard to believe.

[ Parent | on HN ]
Re:Cover Your Tracks by spijdar on Saturday November 21, 2020 @12:40PM (#25171169)
It's actually an interesting case study how "identical installs" often have minor config variations which produce a sort of chaos in the end result. Also, staggered downstream distribution of software updates doesn't help.

I haven't tested it much myself, but I suspect there's a lot to unpack here.

[ Parent | on HN ]
Re:Cover Your Tracks by justaj on Saturday November 21, 2020 @08:30AM (#25169642)
Wait, isn't font rendering client-side? Why would the server have to know how fonts are rendered on my end?
[ Parent | on HN ]
Re:Cover Your Tracks by matsemann on Saturday November 21, 2020 @09:34AM (#25169926)
They render it to a canvas, webgl or similar, and read the pixel data using javascript.
[ Parent | on HN ]