# Conversations (F-Droid build) / TLS 1.3 channel binding deadlock with LDAP backends

**URL:** <https://forum.yunohost.org/t/conversations-f-droid-build-tls-1-3-channel-binding-deadlock-with-ldap-backends/43280>\
**Category:** Support\
**Tags:** xmpp, french, english\
**Created:** [October 30, 2026, 4:26pm UTC](https://forum.yunohost.org/t/conversations-f-droid-build-tls-1-3-channel-binding-deadlock-with-ldap-backends/43280 "2026-10-30T16:26:22Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![tmb](https://forum.yunohost.org/letter_avatar_proxy/v4/letter/t/7c8e57/32.png) [@tmb](https://forum.yunohost.org/u/tmb)\
**Post date:** [October 31, 2026, 10:57am UTC](https://forum.yunohost.org/t/conversations-f-droid-build-tls-1-3-channel-binding-deadlock-with-ldap-backends/43280/3 "2026-10-31T10:57:49Z")

</div>

Hm, that’s really an unfortunate breakage/regression.

Also @TabTwo, is there a way this new SCRAM/LDAP challenge response auth could provide group/role membership information as well?

For example, to be directly usable for permissions in cases like galene videoconferencing rooms, as discussed in [[Galène] Videoconferencing server - #44 by tmb](https://forum.yunohost.org/t/galene-videoconferencing-server/14730/44) ?

---

_[View the full topic](https://forum.yunohost.org/t/conversations-f-droid-build-tls-1-3-channel-binding-deadlock-with-ldap-backends/43280)._