Here’s a simple mitigation — don’t have your encryption depend on 2022 + 23823 being compared to 2022 + 24436. The idea that a cpu frequency change (based on c

Here’s a simple mitigation — don’t have your encryption depend on 2022 + 23823 being compared to 2022 + 24436. The idea that a cpu frequency change (based on cpu load) could be detected, and if detected — that it could lead to any useful information by an attacker is laughably preposterous. The only theoretical vulnerability is if someone in a shared data center was able to gain control over a system on dedicated hardware that had nothing else running on it — exploit some code on it that triggers and expected frequency — open the cage and case, detects the frequency (by turning off all other hardware in the vicinity — meaning you already know which machine it is) and then by exploiting the machine you already control (and have already isolated) you can then physically identify the machine you have exploited.