3 ms·
All libraries we use are constant time. What’s constant time? Crypto libraries need to do operations to encrypt and decrypt your data. The simple, naive implem
by nindalf 4y ago
All libraries we use are constant time.
What’s constant time? Crypto libraries need to do operations to encrypt and decrypt your data. The simple, naive implementation of these operations will work - giving correct input and output. However, a person can time the operation being performed and learn about the key being used. If you’ve deployed on a server and the other person can submit any text they want, whenever they want, they would be able to extract the key from your naive implementation. That’s bad, the worst outcome possible.
That’s why good libraries will make sure that these operations take the same amount of time, regardless of input. So we thought we were safe.
And now these authors tell us, no. That’s not the case. The guidelines used by crypto library developers don’t protect against the attack being described here.
- Zamicol 4y ago>All libraries we use are constant time. Well, except anything Javascript. "Node.js’s crypto libraries do not provide constant-time guarantees and, unfortunately, are still at the mercy of the JavaScript GC" https://cseweb.ucsd.edu/~dstefan/pubs/renner:2018:ct-wasm.pdf https://cseweb.ucsd.edu/~dstefan/pubs/renner:2018:ct-wasm.pd...