Re:Homomorphic encryption implementation
by anonymousDan on Thursday May 22, 2014 @04:54PM
(#7786454)
Can you expand a bit more on the type of commercial agreements and confidentiality requirements of Boeing? In particular, what kind of data would the agreements pertain to, and who would the other parties be? Would the 'hoops' occur only for internal data transmission, or is it because they need to share it with 3rd-party organisations? I'm a researcher in the area, and I'm familiar with stuff like that from the healthcare domain, where you have e.g. lots of different hospitals that want to share certain data for research purposes, but I'm curious as to the use cases more commercial organisations might have.
Yup - Ars can explain it better than me!
http://arstechnica.com/information-technology/2014/04/how-bo...
Clearly, though, this would be a case where homomorphic encryption would not be required - because they've solved the problem without it.
Boeing's technique sounds more like steganography than cryptography.
It's neither. They make the assumption that their combined cloud partners aren't all in cahoots, and distribute their data such that the probability that a) one can intercept enough chunks and b) one can infer meaning from the chunks is very low.
The cynical part of me wants to say that it's very similar to a standard mapreduce, and the security properties came for free/very little.
I think you are wrong. Google's current business requires that they are able to match your interests to ads. Contrary to popular belief, it has nothing to do with selling you out to advertisers and it doesn't even strictly require Google to know all about you.
If they can efficiently apply FHE to your data and produce an encrypted set of ads that only you can unscramble, they'll make plenty of money.
It's not at all clear that this is feasible, but if I had billions of dollars burning a hole in my pocket, I'd probably fund FHE research.
No, it relies on them being able to do that, but also to be able to improve their products such that they stay relevant. Things like A/B testing require Google to know what the user is doing in order to test their effectiveness - a FHE setup would ruin that.
In any case, I'm not sure how this would stop them from tracking in the first place.
No, the people for which this is really useful is large non-IT companies like Boeing or healthcare companies etc. They have huge data processing or storage requirements, and frequently have to run around hoops in order to ensure data is not transmitted in a way that would breach commercial agreements or confidentiality requirements. The problem is that frequently these workloads (especially for companies like Boeing) will involve much data, and HE tends to come with a large size increase and performance drop - so it's often too costly, which is a shame.