The cr.yp.to microblog: 2012.06.30 10:20:10

2012.06.30 10:20:10 (218982246395293696) from Daniel J. Bernstein, replying to "Paulo Barreto (@pbarreto)" (218754457247289345):

@pbarreto @cryptopathe Hardware leakage (e.g., power consumption) is tricky. NaCl eliminates software leakage (cache, branch unit, etc.).

Context

2012.06.29 02:14:41 (218497681516003329) from "Paulo Barreto (@pbarreto)":

@hashbreaker According to @cryptopathe, NaCl has no built-in protection against fault and leakage(!) attacks. Comments? http://crypto.junod.info/hashdays10_talk.pdf

2012.06.29 17:58:56 (218735312229244929) from Daniel J. Bernstein, replying to "Paulo Barreto (@pbarreto)" (218497681516003329):

@pbarreto @cryptopathe Your CPU _will_ spill its secrets to a physical attacker torturing it with electrical probes, heat guns, and lasers.

2012.06.29 19:15:01 (218754457247289345) from "Paulo Barreto (@pbarreto)":

@hashbreaker @cryptopathe What about leakage leakage leakage? ;-)