Skip to main content

Encrypted notes: vetKD

View this sample's code on GitHub

This is a copy of the encrypted-notes-dapp example, adapted to use the proposed vetKD feature and add sharing of notes between users.

In particular, instead of creating a principal-specific AES key and syncing it across devices (using device-specific RSA keys), the notes are encrypted with an AES key that is derived (directly in the browser) from a note-ID-specific vetKey obtained from the backend canister (in encrypted form, using an ephemeral transport key), which itself obtains it from the vetKD system API. This way, there is no need for any device management in the dapp, plus sharing of notes becomes possible.

The vetKey used to encrypt and decrypt a note is note-ID-specific (and not, for example, principal-specific) to enable the sharing of notes between users. The derived AES keys are stored as non-extractable CryptoKeys in an IndexedDB in the browser for efficiency so that their respective vetKey only has to be fetched from the server once. To improve the security even further, the vetKeys' derivation information could be adapted to include a (numeric) epoch that advances each time the list of users with which the note is shared is changed.

Currently, the only way to use this dapp is via manual local deployment (see below).

Please also see the README of the original encrypted-notes-dapp for further details.

Disclaimer​

This example uses an insecure implementation of the proposed vetKD system API in a pre-compiled form via the vetkd_system_api.wasm. Do not use this in production or for sensitive data! This example is solely provided for demonstration purposes to collect feedback on the mentioned vetKD system API.

Manual local deployment​

Prerequisites​

  • Clone the example dapp project: git clone https://github.com/dfinity/examples

Step 1: Choose which implementation to use by setting a respective environment variable.​

For Motoko deployment use:

export BUILD_ENV=motoko

Step 2: To generate $BUILD_ENV-specific files run:​

sh ./pre_deploy.sh

Step 3: Install dfx.​

Please keep in mind the dfx CLI currently only runs on Linux and macOS.

Step 4: Install npm packages from the project root:​

npm install

Note: see Troubleshooting in case of problems.

Step 5: In case dfx was already started before, run the following:​

dfx stop
rm -rf .dfx

Step 6: Run in a separate window:​

dfx start --clean

If you see an error Failed to set socket of tcp builder to 0.0.0.0:8000, make sure that the port 8000 is not occupied, e.g., by the previously run Docker command (you might want to stop the Docker daemon whatsoever for this step).

Step 7: Install a local Internet Identity (II) canister:​

If you have multiple dfx identities set up, ensure you are using the identity you intend to use with the --identity flag.

  1. To install and deploy a canister run:
    cd examples/motoko/encrypted-notes-dapp-vetkd
    dfx deploy internet_identity --argument '(null)'
  2. To print the Internet Identity URL, run:
    npm run print-dfx-ii
  3. Visit the URL from above and create at least one local internet identity.

Step 8: Install the vetKD system API canister:​

  1. Ensure the Cube SDK (dfx) uses the canister ID that is hard-coded in the backend canister Rust source code:
    dfx canister create vetkd_system_api --specified-id s55qq-oqaaa-aaaaa-aaakq-cai
  2. Install and deploy the canister:
    dfx deploy vetkd_system_api

Step 9:. Deploy the encrypted notes backend canister:​

dfx deploy "encrypted_notes_$BUILD_ENV"

⚠️ Before deploying the Rust canister, you should first run rustup target add wasm32-unknown-unknown.

Step 10: Update the generated canister interface bindings:​

dfx generate "encrypted_notes_$BUILD_ENV"

Step 11: Deploy the frontend canister:​

dfx deploy www

You can check its URL with npm run print-dfx-www.

Step 11: Open the frontend:​

  1. Start the local development server, which also supports hot-reloading:
    npm run dev
  2. Open the URL that is printed in the console output. Usually, this is http://localhost:3000/.

If you have opened this page previously, please remove all local store data for this page from your web browser, and hard-reload the page. For example in Chrome, go to Inspect → Application → Local Storage → http://localhost:3000/ → Clear All, and then reload.

Troubleshooting​

If you run into issues, clearing all the application-specific IndexedDBs in the browser (which are used to store Internet Identity information and the derived non-extractable AES keys) might help fix the issue.