Re:Machine Learning on Encrypted Data Without Decrypting It
by jeltz on Tuesday November 26, 2019 @02:17PM
(#21641614)
What about side effects? Does eg timing of the computations leak data?
Re:Machine Learning on Encrypted Data Without Decrypting It
by jrockway on Tuesday November 26, 2019 @04:28PM
(#21642929)
I would expect that all data processing by default leaks information via computation time. Some algorithms are intentionally designed to resist this; people that have gone to this effort will mention them. (A similar thing: assume something is not thread-safe unless the documentation mentions it's thread-safe.)
The person you're responding to is correct. It's an explicit design goal that a fully homomorphic encryption system would not expose any distinguishable oracle about the underlying data. Otherwise there would be no point to it whatsoever, because you'd just be performing the same computations on the data dramatically less efficiently and without any benefit.
This follows the general imperative of cryptography, which is that the outputs of cryptographically secure primitives (hash functions, pseudorandom generators, pseudorandom permutations, etc) should be computationally indistinguishable from random up to 2^n queries, for some large n (such as 128).