Re:How I implemented my own crypto
by loup-vaillant on Thursday August 03, 2017 @05:41AM
(#14918181)
I believe padding the timing always has been considered a bad idea. If you want to guarantee you won't exceed the timing, you probably have to take so much margin that your primitive becomes prohibitively slow. And I'm not even sure it would protect you against cache timing attacks.
Simply put, there are easier and cheaper ways to guarantee timings. Perhaps Haskell is even capable of harnessing them. (I'm thinking of the usual "no secret dependent branches", and "no secret dependent indices".)
Re:How I implemented my own crypto
by Ded7xSEoPKYNsDd on Thursday August 03, 2017 @05:57AM
(#14918252)
Random delays do not protect against timing attacks. Best thing it can do, is to force the attacker to collect a few more timing samples. (To the point where the the random noise averages itself out.)
Edit: Whoah, why the hate? :(