From 134c51116dbba7a430fccaa1f2cbdc545e4e8281 Mon Sep 17 00:00:00 2001 From: steveluscher Date: Fri, 8 Dec 2023 23:10:05 +0000 Subject: [PATCH] Note, in the README, that polyfilled `CryptoKeys` can not be stored in IndexedDB Closes #1911 --- packages/webcrypto-ed25519-polyfill/README.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/packages/webcrypto-ed25519-polyfill/README.md b/packages/webcrypto-ed25519-polyfill/README.md index 3e0f80c9f62f..6a48610b37dc 100644 --- a/packages/webcrypto-ed25519-polyfill/README.md +++ b/packages/webcrypto-ed25519-polyfill/README.md @@ -19,6 +19,9 @@ This package contains a polyfill that enables Ed25519 key manipulation in enviro > [!WARNING] > Because this package's implementation of Ed25519 key generation exists in userspace, it can't guarantee that the keys you generate with it are non-exportable. Untrusted code running in your JavaScript context may still be able to gain access to and/or exfiltrate secret key material. +> [!NOTE] +> Native `CryptoKeys` can be stored in IndexedDB but the keys created by this polyfill can not. This is because, unlike native `CryptoKeys`, our polyfilled key objects can not implement the [structured clone algorithm](https://www.w3.org/TR/WebCryptoAPI/#cryptokey-interface-clone). + ## Usage Environments that support Ed25519 (see https://github.com/WICG/webcrypto-secure-curves/issues/20) do not require this polyfill.