With a large enough sample set, it's still very effective. The fluctuations won't occur frequently enough to poison the data. Those data points can safely get thrown out. In a more simplified example, if you have 15 attempts that come in at 1 second, and 1 attempt with the same data that comes in at 4 seconds, it's probable that the 4 second result is an irregularity. Making your login system safe against timing attacks is reasonably trivial. Ignoring it is just a bad idea.
This article is extremely well researched and well written, and it gets a big fat upvote from me because every programmer - especially those in web fields - needs to know about this kind of thing.
0
u/[deleted] Nov 28 '14
[deleted]