4 ms·
Homomorphic computing is not mentioned...?
by russfink 6y ago
Homomorphic computing is not mentioned...?
- topspin 6y agoIt's a product announcement by a Google employee and they're not selling homomorphic computing. They're selling a different product.
- ackbar03 6y agoIm not a cryptography expert but from what i've learnt about homomorphic encryption in my courses its nowhere close to being usable at reasonable speeds
- Joker_vD 6y agoYeah, turning 1 bit of plaintext into 20 MB of ciphertext kills any hope for "reasonable speed". I have a toy functional language implementation that has no built-in data structures whatsoever, and even it in the end represents a bit only as an 8-byte closure.
- ssmiler 6y agoMaybe in batched HE schemes. In https://github.com/tfhe/tfhe https://github.com/tfhe/tfhe the ratio is much smaller, 2.5kB per plaintext bit.
- anonymousDan 6y agoThis is actually practical for general workloads. Homomorphic encryption not so much (although there have been advances for machine learning inference recently)
- gumby 6y agoSeveral orders of magnitude slower. Run in in a Secure Enclave (like SGX) you run at full speed.
- llarsson 6y agoBetter speed, yes, but also, SGX has been broken in different ways and just a few days ago, Apple's secure enclave for phones was broken, too. These are extra obstacles along the way, but not insurmountable walls.
- ilaksh 6y agoWhy would people downvote the most insightful comment? Surely it is on topic to mention the next level of protection? I believe that we need a new paradigm for voting in threads because people are consistently using it poorly.