News for hackers. Stuff that matters.
Re:Hot Pixels: Frequency, Power, and Temperature Attacks on ... by Szpadel on Tuesday May 30, 2023 @05:13PM (#36130892)
for me at least this is very useful on search results like on Google when i try to find again something i found before but until now not needed it.

maybe better would be to limit styling just to color and when programmatically checked return value that should be when this class would be not present

Re:Hot Pixels: Frequency, Power, and Temperature Attacks on ... by snovv_crash on Tuesday May 30, 2023 @05:55PM (#36131488)
I think it would make sense to track this with a separate database for every host domain. Either that or have a user-only rendering layer which applies the colors, but which isn't visible to any scripts that are running.
Re:Hot Pixels: Frequency, Power, and Temperature Attacks on ... by nine_k on Tuesday May 30, 2023 @07:21PM (#36132512)
Hiding the result of rendering from scripts by default is indeed reasonable, and is being done (see "tainted canvas").

This exploit avoids lookig directly at pixels, because the pixels are not available. It runs an SVG filter on these pixels, without looking at the result of filtering; it just measures how much time / energy did it take to render.

Re:Hot Pixels: Frequency, Power, and Temperature Attacks on ... by nine_k on Tuesday May 30, 2023 @06:57PM (#36132255)
Styling with color is the key part of the exploit.

There should be no styling based on the browser history, shared across pages, or such history will be exfiltrated.