Think about how much benefit we gained during that time. And even then, anyone running in a trusted environment would rather have the optimization consequences be damned. Do you think HFTs patched their boxes to criple their perfomance? No.
Sure, now we know it's a problem we'll offer solutions for people who really need it. But it'll be a long while before the average person needs to think about this and in the meantime billions of people benefitted from better CPUs.
...because Intel placed profit above user's needs and choose not to allow ECC on desktops.
Similarly, many other things have been made insecure by plain greed.
[1] https://static.googleusercontent.com/media/research.google.c...
How many corrupt files, strange bugs, or quirks can be attributed?
Except it did.
The programs who funded the research for telephones, lasers, aeronautics, satellites, CDs, fiber optics, GPS, GSM, LCDs using tax money?
I can imagine how little progress there would be if they didn't.
Maybe we can introduce a new set of instructions that are guaranteed to be constant time, but good luck convincing the compiler/language/OS to use these slower instructions even if just for the code that is important for security.
We got proactive constant time on a lot of cryptographic operations.
The problem is, it's not constant power.. and DFS provides a window by which you can make remote power measurements.
Downthread: https://news.ycombinator.com/item?id=31745105
Seriously, this has been talked about for ages now. If every platform had a good enough FPGA, it could be used for cryptography and/or to accelerate some specific computations. Abd without having a set of algorithms baked into the silicon, it would not make the device eventually obsolete as the world moves to better algorithms.
Edit: > it would not make the device eventually obsolete as the world moves to better algorithms
Ah there I found it. Makes sense to buy the FPGA manufacturers, so they devices still become obsolete and people buy their newer processors.
The need for constant time should have first class support on the language/compiler level, the OS level, the ISA level, and the hardware level. E.g. the processor could guarantee that the instructions of a certain section of code are executed at a constant rate, the OS could guarantee that the thread remains pinned to one core and the frequency fixed, and the compiler could guarantee that only branchless assembly gets emitted.