Ask for the recovery key at sign-in; failed decryptions stay failed #32

New issue

Open

opened 2026-10-05 19:03:38 +00:00 by robocub · 0 comments

robocub commented

2026-10-05 19:03:38 +00:00

Owner

Upstream: commetchat/commet#1046

Commet doesn't ask for the recovery key or backup passphrase during sign-in. It goes straight to the room list, every message rendered before keys arrive is cached as Failed to decrypt, and entering the key later doesn't repair them (only per-message retries do). Element and FluffyChat ask for the key right after the password.

Two parts: (1) a recovery-key step in the login flow; (2) re-attempt decryption for UTDs when keys arrive (backup restore or forwarded keys). Part 2 overlaps our #16.

Imported from Commet's tracker during the 2026-10-05 triage. As of that date it was open upstream with no assignee and no open PR. Nothing gets posted back to their tracker. If upstream fixes it first, close this issue and drop our patch on the next rebase (record the change in VOMMET_CHANGES.md).

Upstream: [commetchat/commet#1046](https://github.com/commetchat/commet/issues/1046) Commet doesn't ask for the recovery key or backup passphrase during sign-in. It goes straight to the room list, every message rendered before keys arrive is cached as *Failed to decrypt*, and entering the key later doesn't repair them (only per-message retries do). Element and FluffyChat ask for the key right after the password. Two parts: (1) a recovery-key step in the login flow; (2) re-attempt decryption for UTDs when keys arrive (backup restore or forwarded keys). Part 2 overlaps our #16. --- *Imported from Commet's tracker during the 2026-10-05 triage. As of that date it was open upstream with no assignee and no open PR. Nothing gets posted back to their tracker. If upstream fixes it first, close this issue and drop our patch on the next rebase (record the change in VOMMET_CHANGES.md).*

robocub added the

bug

effort: large

upstream

labels

2026-10-05 19:03:38 +00:00