Hacker News Reader

How do you prevent side channel attacks that leak secrets, implementations, or even affect other scripts random number generation?

Given the comfort in the bug bounty, and that bugs are inevitable, it seems like cloudflare is willing to risk some exposure to upcoming exploits. How do you feel about this in an era of sophisticated nation states that I’m sure would have a keen interest in being “inside” cloudflare?

View on HN

Please see the comment I linked about Spectre specifically: https://news.ycombinator.com/item?id=18280156

I actually think our approach to Spectre -- focusing on preventing the observation of the side channel, rather than blocking speculation -- is likely to be more robust against Spectre variants that haven't been revealed yet. Case in point, we developed some of our core mitigations before we knew about Spectre at all.

Spectre affects containers and VMs too.

Specter is one class of side channel attack. When you’re in process, I presume there will likely be many more. I meant it as a more general question.

Reply on news.ycombinator.com