News for hackers. Stuff that matters.
Re:Hertzbleed Attack by kevingadd on Tuesday June 14, 2022 @02:35PM (#31743882)
The frequency change is observable by the whole algorithm taking a different time to run - the algorithm is constant-time, but because the clock speed is changing based on the data, it's not constant-wall-clock-time and you can perform a timing attack.
Re:Hertzbleed Attack by karussell on Tuesday June 14, 2022 @02:49PM (#31744132)
And also when I set the scaling governor to "performance" (under Linux)? Is the frequency in that case still adjusted based on the data or always "maximum"?
Re:Hertzbleed Attack by adrian_b on Tuesday June 14, 2022 @03:44PM (#31744986)
With the performance governor, the clock frequency is continuously adjusted between the "base frequency" and the "maximum turbo frequency", e.g. between 3.7 GHz and 4.8 GHz, for my computer.

With the powersave governor, the clock frequency is continuously adjusted between a frequency much lower than the "base frequency", and also the "maximum turbo frequency", e.g. between 2.2 GHz and 4.8 GHz, for my computer.

Re:Hertzbleed Attack by pyrolistical on Tuesday June 14, 2022 @03:24PM (#31744695)
Haha so constant time algorithm isn’t constant time
Re:Hertzbleed Attack by jaza on Tuesday June 14, 2022 @11:16PM (#31748739)
Time itself isn't constant, so arguably a constant time algorithm is an oxymoron! But that's a whole 'nother topic.