Skip to content

6.4.18#1555

Merged
tmolitor-stud-tu merged 29 commits intostablefrom
beta
Feb 8, 2026
Merged

6.4.18#1555
tmolitor-stud-tu merged 29 commits intostablefrom
beta

Conversation

@github-actions
Copy link

@github-actions github-actions bot commented Jan 21, 2026

  • Fixed crash when receiving broken OMEMO bundles
  • Better fix for audio/video codec issues (aka black video stream)
    IOS_ONLY - Fixed broken video calls by fixing bug in Mozilla's webrtc-sdp library
  • Reworked complete OMEMO trust management
  • Fixed spurious "new OMEMO device found" notifications and status messages
  • Introduced some new OMEMO expert settings
  • Improved UI responsiveness in some rare cases
  • Made sure to periodically advance the OMEMO DH-ratchet even on devices only used for receiving messages, not sending
  • Made sure to remove old OMEMO devices not seen for more than 90 days from own devicelist

tmolitor-stud-tu and others added 22 commits January 9, 2026 14:03
Introduce a new expert setting to ignore all ToFu-only members in encrypted
groups once at least one member isn't ToFu-only anymore.

Introduce a new expert setting to drop calls not being omemo-verified.
This reverts commit 2b8e6e3.

This commit was applied because many users complained that encryption
was "broken" after verifying a fingerprint and then migrating to or adding a
new device.

This was a UX decision and we tried to mitigate the security impact by
informing the users about new devices, both in their own account (as
push notification) as well as for the contacts they were chatting with
(as yellow status message in the chat itself).
Users that cared about security could then manually disable trust for
these new devices.

In the hope that users are now more familiar with trust management, we
now revert this commit and introduce a new setting to switch between the
"better UX" one and this one in a new commit.
--> force a key transport message with 1% probability (~ every 100th message)
If that device is still active, it will readd itself to the devicelist
again.
This should fix this crash:
CRASH(NSInternalInconsistencyException): attempt to insert row 0 into
section 1, but there are only 0 rows in section 1 after the update
Sometimes ejabberd sends a mam fin element with complete=false, but
missing rsm last element. Interprete those results as complete=true,
too.
IOS_ONLY - Fixed broken video calls by fixing bug in Mozilla's
webrtc-sdp library
- Reworked complete OMEMO trust management
- Fixed spurious "new OMEMO device found" notifications and status
messages
- Introduced some new OMEMO expert settings
- Improved UI responsiveness in some rare cases
- Made sure to periodically advance the OMEMO DH-ratchet even on devices
only used for receiving messages, not sending
- Made sure to remove old OMEMO devices not seen for more than 90 days
from own devicelist
This fixes the real cause for the black video bug.
- Better fix for audio/video codec issues (aka black video stream)
- Fixed crash when receiving broken OMEMO bundles
The last fix was incomplete, thanks Isadora.
- Fixed crash on broken OMEMO bundles again
@tmolitor-stud-tu tmolitor-stud-tu merged commit 3930682 into stable Feb 8, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

Comments