Bug 57604 - Handle passwords in MUC invites
Summary: Handle passwords in MUC invites
Status: RESOLVED MOVED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: gabble (show other bugs)
Version: git master
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-27 11:01 UTC by Will Thompson
Modified: 2019-12-03 19:58 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Will Thompson 2012-11-27 11:01:57 UTC
MUC invites can contain the password required to join the room <http://xmpp.org/extensions/xep-0045.html#invite>. Right now Gabble ignores them completely.

For starters, Gabble should pull the password out of invitations it receives, and then use it when joining the channel if the user accepts the invitation.

When inviting people to rooms, we use mediated invitations (sent by the server) which is supposed to fill in the password for us, so we don't have to worry about that. If we were ever to send direct invitations <http://xmpp.org/extensions/xep-0249.html> we would have to worry about this again.

To let the UI/user know the password for future use, it could do worse than set <http://telepathy.freedesktop.org/spec/Channel_Interface_Room_Config.html#Property:Password> to the password. (There's no space in LocalPendingInfo to store the password along with the invitation, but hey.)
Comment 1 GitLab Migration User 2019-12-03 19:58:24 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-gabble/issues/252.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.