Constant-Time Code: The Pessimist Case (eprint.iacr.org)
from tedu@inks.tedunangst.com to inks@inks.tedunangst.com on 08 Mar 06:09
https://inks.tedunangst.com/l/5184

This note discusses the problem of writing cryptographic implementations in software, free of timing-based side-channels, and many ways in which that endeavour can fail in practice. It is a pessimist view: it highlights why such failures are expected to become more common, and how constant-time coding is, or will soon become, infeasible in all generality.

From compiler optimizations to CPU pipelines and register renaming.

#compiler #cpu #crypto #paper #pdf #perf #programming #turtles

#compiler #cpu #crypto #inks #paper #pdf #perf #programming #turtles