Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • G gajim-plugins
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 51
    • Issues 51
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 5
    • Merge requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gajim
  • gajim-plugins
  • Issues
  • #326

Closed
Open
Created Jun 17, 2018 by Michel Le Bihan@mimi89999

Messages are encrypted for removed MUC members

Versions

  • OS: Debian GNU/Linux testing (buster)
  • Gajim version: Latest commit on messagewindow branch
  • GTK version: 3.22.29
  • Python-nbxmpp version: 0.6.6
  • OMEMO plugin: 2.5.13

Steps to reproduce the problem

  1. Create a MUC, add members, enable OMEMO, send some messages, etc.
  2. Remove a member
  3. Send a message

Expected behavior

Message should only be encrypted for current members.

Only fingerprints of current members should be shown in the fingerprints menu.

Actual behavior

Message is also encrypted for removed MUC members.

Fingerprints of removed MUC members are shown in the fingerprints menu.

Assignee
Assign to
Time tracking