&quot;Secure computation is a catch-all term for cryptographically safe computation; this includes ORAM schemes, FHE, iO, Searchable Symmetric Encryption, PIR, etc.&quot;<p>I&#x27;m aware that they have all kinds of interesting models. I even have papers on a few of those. I&#x27;m also aware cryptographers often ignored concrete details of their ideas in ways that led to real-world vulnerabilities. This happened with padding, covert channels, implementation difficulties, and so on.<p>&quot;If you mock without knowing, you&#x27;re the fool.&quot;<p>I said it&#x27;s called Secure, Multiparty Computation in most discussions of this stuff if it&#x27;s crypto letting two or more work together on something often with confidentiality but sometimes just integrity. That was the label where I first saw it in Schneier&#x27;s book all the way up to an article I saw after this one. Are you saying the concept is not called multiparty computation?<p>Or are you saying that anyone publishing cryptographic papers has factored into their math assumptions and effects of host CPU&#x27;s, caches, interrupts, I&#x2F;O, compilers, networks, and users? <i>That</i> would be a mock-worthy claim. Those ground in practical reality and useful are rare enough that I post them on Schneier&#x27;s blog and here to bring attention to them. Incidentally, ORAM and CryptDB were among those I posted worth exploring for potential, real-world benefit. ;)<p>Note: I did critique CryptDB as not good enough against NSA as some media portrayed it. It relies on underlying host, software running on it, and distribution of both. NSA has been smashing such things. So, if A then B, the dependency shows it&#x27;s insecure against such a High Strength Attacker. Good for many others and still potential here, though.