Lee Danilek

2 years ago

End-to-End Encryption with Convex

What's the maximum level of privacy an application can offer? Platforms like Convex encrypt data at rest but allow you to interact with it in unencrypted form via user-defined functions running on the server. This is tremendously useful but occasionally there's data that you don't want to exist in unencrypted form anywhere.

Consider a scenario where I need to send a crypto passphrase to my partner. That passphrase should be encrypted on a computer that I control, decrypted on a computer my partner controls, and not be accessible anywhere else. This is called end-to-end encryption, because only the endpoints of the communication — my partner and I — can see the secret passphrase.

I wanted to see what it would take to build end-to-end encryption on top of Convex, so I built Whisper.

How to use Whisper

Check out https://whisper-convex.vercel.app/, the final product.

Screenshot of the app in use

1. Type in a secret message
2. The message is encrypted with an optional client-side password and stored in Convex.
3. Send the private URL to the recipient(s), through an external secure channel.
4. A recipient retrieves the encrypted message from Convex, and decrypts the message in their browser.

Features:

1. No login or setup, for either the sender or recipient.
2. In case the URL is intercepted, the sender can see the IP address of everyone who uses the URL to read the secret message, in a list that reactively updates.
3. The message expires after a certain number of accesses, or a configurable duration.
4. When the message expires, a scheduled mutation deletes it from Convex so no one can access it, even with the URL.

How Whisper works

The full source code is at https://github.com/ldanilek/whisper, and I’ll highlight some of the key components here.

To create a Whisper — an encrypted secret message — we use AES symmetric encryption before calling the createWhisper mutation in Convex. This code runs in the browser, so the raw URL and secret are never sent to Convex.

1if (password.length === 0) {
2  password = uuid.v4();
3}
4const encryptedSecret = CryptoJS.AES.encrypt(secret, password).toString();
5const passwordHash = hashPassword(password);
6await createWhisperMutation(
7	name, encryptedSecret, passwordHash, creatorKey, expiration,
8);
9

Accessing the Whisper requires password hash to match, and it’s a mutation so the access can be recorded. This code runs in a transaction on Convex servers.

1// accessWhisper.ts
2export default mutation({
3  args: {
4      whisperName: v.string();
5      passwordHash: v.string();
6      accessKey: v.string();
7      ip: v.union(v.string(), v.null());
8  },
9  handler: async (
10    { db },
11    {
12      whisperName,
13      passwordHash,
14      accessKey,
15      ip,
16    }
17  ) => {
18    const whisperDoc = await getValidWhisper(db, whisperName, true);
19    if (!timingSafeEqual(whisperDoc.passwordHash, passwordHash)) {
20      throw Error("incorrect password");
21    }
22    await db.insert("accesses", {
23      name: whisperName,
24      accessKey,
25      ip,
26    });
27  },
28});
29

Once the access is registered, we use a Convex query to read the encrypted message, and AES to decrypt it.

1const SecretDisplay = ({name, accessKey, password}) => {
2  const encryptedSecret = useQuery(api.readSecret.default, name, accessKey);
3  return <div>{
4    encryptedSecret ?
5		CryptoJS.AES.decrypt(encryptedSecret, password).toString(CryptoJS.enc.Utf8) 
6		: "Loading..."
7  }</div>;
8}
9

To delete expired secrets, we schedule a mutation to delete the encrypted message.

1// inside createWhisper.ts
2await scheduler.runAt(expireTime, internal.deleteExpired.default, whisperName, creatorKey);
3// inside expireNow.ts
4await db.patch(whisperDoc!._id, {
5  encryptedSecret: "",
6});
7