assuming the handler function is encrypted to match.
Yeah, this is the thing I’m doubting / don’t understand how that would work.
E.g. A* / navigation problems.
You send private start and goal points.
Either the stuff is truly private, then the program can’t read it.
Or the program can read it, but then the owner of the machine the program runs on can just read it from memory.
It doesn’t matter if it says “45124x5234234fgasdgf” or “Paris”, because the program state will identify that. Even if you encrypt the entire location database (with stuff that’s then fully known to the server) and it will still look up “45124x5234234fgasdgf” and the server can trivially decrypt that.
check out apple’s homomorphic encryption page
Interesting, but I’m more leaning on “they have a vested interest to lie about this” rather than “surely this is correctly working tech that keeps me safe”. Like Amazons “AI supermarket” that was just a bunch of indians doing video surveillance.
And their explanation makes the same amount of sense as the blog post. I have no doubt that it can work for simple commutative math operations, over “smooth” domains. Where my doubt comes in is functions where the encryption would cause the operation to take place outside of the domain bounds.
How does an encrypted asin or acos work?
Anyway, thanks for the answer, I was recently impressed by GNU Taler, which also did something cryptographic stuff I didn’t think was possible. So I’m not saying this is heresy and can’t be done and trying to say it will work is forbidden, I just don’t think the explanations so far are detailed enough.
Yeah, this is the thing I’m doubting / don’t understand how that would work.
E.g. A* / navigation problems.
You send private start and goal points.
Either the stuff is truly private, then the program can’t read it.
Or the program can read it, but then the owner of the machine the program runs on can just read it from memory.
It doesn’t matter if it says “45124x5234234fgasdgf” or “Paris”, because the program state will identify that. Even if you encrypt the entire location database (with stuff that’s then fully known to the server) and it will still look up “45124x5234234fgasdgf” and the server can trivially decrypt that.
Interesting, but I’m more leaning on “they have a vested interest to lie about this” rather than “surely this is correctly working tech that keeps me safe”. Like Amazons “AI supermarket” that was just a bunch of indians doing video surveillance.
And their explanation makes the same amount of sense as the blog post. I have no doubt that it can work for simple commutative math operations, over “smooth” domains. Where my doubt comes in is functions where the encryption would cause the operation to take place outside of the domain bounds.
How does an encrypted asin or acos work?
Anyway, thanks for the answer, I was recently impressed by GNU Taler, which also did something cryptographic stuff I didn’t think was possible. So I’m not saying this is heresy and can’t be done and trying to say it will work is forbidden, I just don’t think the explanations so far are detailed enough.