Earlier quoted context omitted.
Homomorphic encryption isn't currently practical, even for small-ish problems. It needs to use constant space, and every operation needs to flip on average half of the bits. There aren't obvious ways around these restrictions, though off hand I can only come up with a quick hand-wavy "proof" that this must always be so if less than one bit of the unencrypted state is to be lost with every state update. So, in order t…
That is only true for fully homomorphic encryption. There are simpler cryptosystems (e.g. ElGamal for a trivial example) that have more constrained homomorphisms that theoretically could be used here.
Google backs off on previously announced Allo privacy feature
131–133 of 133 posts
Re: Google backs off on previously announced Allo privacy feature
#132>Allo messages will still be encrypted between the device and Google servers, and stored on servers using encryption that leaves the messages accessible to Google’s algorithms. 'using encryption that leaves the messages accessible to Google’s algorithms' So, not meaningfully encrypted at all then?
Probably stored under the same security infrastructure as Gmail and hangouts messages. Which, IIRC, means no human is given direct access without the account holder's permission. Algorithms are allowed access, but only if they emit data that is similarly secured, or emits data in aggregate (where, I think, aggregate was defined as 100k+ users per aggregate data point) It's extremely hard for a Googler or product team…
Re: Google backs off on previously announced Allo privacy feature
#133Earlier quoted context omitted.
That's easy, TLS is great for Google as ISPs and wifi providers can't replace ads with their own in transit.
That is some Alex Jones level reasoning. There's no end-user security you can provide that can't be reframed that way.