Untrusted keys block MUC messages with OMEMO #12

New issue

Open

opened 2026-11-01 03:18:50 +00:00 by bmt · 1 comment

bmt commented

2026-11-01 03:18:50 +00:00

Member

build: anotherim-js 0.7.18, libtacky 1.1.18

With OMEMO turned on in a MUC, one member without a trusted key blocks the sender's message for everyone.
steps:

A MUC with OMEMO turned on and members without a trusted key.
Send a message to the MUC.

expected: The message is delivered to members with usable keys, and the sender sees which members did not get it
actual: The message is not delivered to anyone and fails with "no usable OMEMO device for …" and a Retry button.

build: anotherim-js 0.7.18, libtacky 1.1.18 With OMEMO turned on in a MUC, one member without a trusted key blocks the sender's message for everyone. steps: 1. A MUC with OMEMO turned on and members without a trusted key. 2. Send a message to the MUC. expected: The message is delivered to members with usable keys, and the sender sees which members did not get it actual: The message is not delivered to anyone and fails with "no usable OMEMO device for …" and a Retry button.

ann commented

2026-11-04 18:54:57 +00:00

Owner

1.2.0-rc2 adds tests for each of those cases and a status flag so the app can tell "some were left out" from "the send was stopped"; app 0.8.0-rc2 uses it, so the "Not sent" banner no longer appears over a message that did go out.

In libtacky 1.1.18 one member without a usable key stopped the whole room send. Since 1.1.19 (app 0.7.21 and later) the message goes to every member with a usable key, and a line under it names the members who did not get it; the send fails only when nobody can read it. Keys that were never verified still receive under blind trust; refused keys and keys that changed unverified do not. 1.2.0-rc2 adds tests for each of those cases and a status flag so the app can tell "some were left out" from "the send was stopped"; app 0.8.0-rc2 uses it, so the "Not sent" banner no longer appears over a message that did go out.