Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Encrypted communication is uni-directional #9

Open
5 tasks
iNPUTmice opened this issue Mar 25, 2016 · 0 comments
Open
5 tasks

Encrypted communication is uni-directional #9

iNPUTmice opened this issue Mar 25, 2016 · 0 comments

Comments

@iNPUTmice
Copy link
Contributor

The issue and the cause is described here: omemo/gajim-omemo#50

Steps to circumvent the problem include:

  • rename add_devices to set_devicesbecause this is what the method actually does. Helps to prevent confusion.
  • rename add_own_devices to set_own_devices (same reason as above)
  • create a new method call add_device(jid, deviceId) (Should not duplicate device ids in the array. Ie treat the array as a set)
  • In decrypt_msg call add_device with sender_jid and sid
  • Somewhere in init (before we connect to a server) add all recipient_id, device_id combos from the litesessionstore to the device_ids array (basically calling set_devices)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant