Skip to the content ForoHackers
Log inJoin

What I do: how computers leak through time and power

CryptographyHardware securityIntroductions
#1102 · sp00ky_s1d3ch4nn3l · · Report

Short intro. I study side channels: the ways a correct program leaks secrets through things it was never meant to say. How long an operation takes, how much power it draws, which cache lines it touches.

I work on this at a conceptual level and in my own lab, with boards and code I wrote myself. The thing I find beautiful is that the algorithm can be mathematically perfect and the leak still exists, because the implementation runs on physics.

If you want a feel for it: comparing a password with an early-exit loop takes slightly longer the more leading characters match. That is a side channel with a for loop and no fancy equipment. I will probably write about that one soon, and about why "constant time" is a property of machine code, not source code.

#1762 · bitflip_betty · · Report

Power analysis is my favourite party trick. The same chip that happily multiplies two numbers draws a different current depending on how many bits flip in the register. Hardware is a very talkative thing, and most of us never ask it anything.

#1763 · n0p_sl3d · · Report

The early-exit compare is a great first example. In CTF terms it shows up as "check the flag one byte at a time and watch the response time". Practice it on your own local challenge binary and you will never write strcmp on a secret again.

Log in or join to reply.