Repository navigation
WebCaller v0.13.0 — Ratcheted messaging and identity verification
New messages, media manifests and call signaling use Vodozemac’s Olm Double Ratchet, bound to existing signed device identities. A server-controlled contact removal can no longer erase the saved verification fingerprint and silently authorize replacement keys.
Reopen or refresh WebCaller on both phones once after upgrading. Accounts, invitations and authorized pre-upgrade history are preserved. Keep browser site storage intact: readable history is separately encrypted on each device, and the server cannot reconstruct discarded transport keys. Newly created messages never silently fall back to the old protocol. Historical v1 messages retain their old security limitations.
Files use independent one-use sessions, each call has its own signaling stream, and key-server requests do not hold the shared crypto lock. Atomic, fenced IndexedDB commits cover multiple tabs, reloads, expiry and deletion. Pinned WASM and dependency licenses ship with the source; no external runtime CDN or new server package is needed.
Validation: 110 deployed-source and 114 public-release tests pass; both exact-commit GitHub CI runs passed, including installers and container builds. Disposable browser checks verified invitations, text/replies, receipts, edits and inline images after reloading both participants. Authenticated WebSocket offer/answer/ICE and delayed file-key requests were tested separately. Physical-phone background ringing, audio routing and battery consumption were not certified by these checks.
This integration remains unaudited and is not Signal wire-compatible or post-quantum. Retained readable local history and malicious same-origin website code remain separate risks. See Security and migration and the beginner installation guide.
Archives contain only the audited source tag. SHA256SUMS.txt verifies the attached downloads.