Title: Hi, creator here.<p>This is a demo of our recent work presented at Oakland (IEEE S&amp;P): <a href="https:&#x2F;&#x2F;eprint.iacr.org&#x2F;2022&#x2F;368" rel="nofollow">https:&#x2F;&#x2F;eprint.iacr.org&#x2F;2022&#x2F;368</a>. The server and client code are written in Rust and available here: <a href="https:&#x2F;&#x2F;github.com&#x2F;menonsamir&#x2F;spiral-rs">https:&#x2F;&#x2F;github.com&#x2F;menonsamir&#x2F;spiral-rs</a>. The general aim of our work is to show that homomorphic encryption is practical today for real-world applications. The server we use to serve this costs $35&#x2F;month!<p>A quick overview: the client uses homomorphic encryption to encrypt the article number that they would like to retrieve. The server processes the query and produces an encrypted result containing the desired article, and sends this back to the client, who can decrypt and obtain the article. A malicious server is unable to determine which article the client retrieved. All search and autocomplete is down locally. The technical details are in the paper, but the high level summary is that the client creates a large one-hot vector of encrypted bits (0’s except for the index of the desired article, where they place a 1) and then the server computes something like a ‘homomorphic dot product’ between the query and the plaintext articles.<p>I’d like to caveat that this is an in-browser demo to show it is practical to use homomorphic encryption at this scale. As a real product, you’d probably want to distribute a signed client executable (or Electron app) since otherwise, a malicious server could simply deliver bad client JS on the fly.<p>Happy to answer any questions!
Upvote: