Skip to content

fix(wasm): return error instead of silently ignoring encryption_key#3798

Open
Sertug17 wants to merge 1 commit into
xmtp:mainfrom
Sertug17:fix/3797-wasm-encryption-key
Open

fix(wasm): return error instead of silently ignoring encryption_key#3798
Sertug17 wants to merge 1 commit into
xmtp:mainfrom
Sertug17:fix/3797-wasm-encryption-key

Conversation

@Sertug17

@Sertug17 Sertug17 commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

Closes #3797

When encryption_key is provided in WASM builds, return a JsError
instead of logging a warning and creating an unencrypted database.
The previous behavior silently exposed sensitive message data in
plaintext without the caller's knowledge.

Note

Return error when encryption_key is provided in WASM builds

Previously, build_store in the WASM client silently ignored encryption_key with a warning log. It now returns a JsError immediately, making the unsupported option visible to callers. Behavioral Change: any WASM code that passes encryption_key will now receive an error instead of proceeding silently.

Macroscope summarized 52a721d.

When encryption_key is provided in WASM builds, return a JsError
instead of logging a warning and creating an unencrypted database.
The previous behavior silently exposed sensitive message data in
plaintext without the caller's knowledge.

Closes xmtp#3797
@Sertug17 Sertug17 requested a review from a team as a code owner June 29, 2026 18:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug(wasm): encryption_key parameter silently ignored, creating unencrypted database

1 participant