Skip to content

WebCaller v0.14.0 — Optional four-word call comparison

Choose a tag to compare

@adlererik adlererik released this 12 Oct 13:08

Four optional call words now appear beside the other person's name, in the same font as the codec information. Call quality sits neatly below the aligned voice/video codec and data-rate rows. Voice and video calls work without reading or confirming the words.

Read all four words to each other, in order, to compare this call's connection. Different words mean you should end the call before sharing sensitive information. The display never claims that people have performed the comparison.

The check uses a separate fresh, committed X25519 exchange and the already bundled Vodozemac SAS primitive, bound to the active call, public identities and accepted DTLS fingerprints. Four 2048-word indices encode 44 bits. There are no new npm dependencies, no export of Olm root/chain secrets, and no change to existing encryption or identity pins. ICE/codec changes retain the words when media identity stays the same. Interrupted or unsupported checks show “Call words unavailable” while the call continues.

SAS state stays in memory; its plaintext frames are excluded from readable history, and the display, accessibility labels, timers and ephemeral objects are cleared at hang-up. This applies to the call check, not to the application's existing encrypted history and identity storage. Browser/OS forensic erasure cannot be guaranteed. This application-specific protocol integration remains unaudited.

Validation: 127 public-project automated tests; 123 isolated tests on the Debian deployment; real two-browser synthetic voice/video calls with matching words, ICE restart and video upgrade continuity, optional-check timeout with continuing Opus audio, hang-up cleanup, and a 390-pixel layout check. Public HTTPS source hashes, no-store responses and authenticated WebSocket upgrade behavior also pass. Physical phone checks remain useful after upgrading.

Upgrade using the existing operations guide. Keep .env, data and browser site storage intact. Reopen or reload the page on both phones once; older clients can still call but cannot display the new comparison.

See Call verification for the complete protocol and limitations. Source archives and SHA256SUMS are attached; they contain generic configuration examples and third-party licenses, with no live server configuration or account data.