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

OMEMO in a MUC #1180

Closed
genofire opened this issue Sep 8, 2018 · 6 comments

Comments

@genofire
Copy link
Contributor

commented Sep 8, 2018

It shows Unencryptable OMEMO message

@genofire

This comment has been minimized.

Copy link
Contributor Author

commented Sep 8, 2018

screenshot from 2018-09-08 13-16-16

@allo-

This comment has been minimized.

Copy link

commented Sep 8, 2018

Same here. Neither incoming messages nor carbons are decrypted. Outgoing messages are encrypted with all relevant keys.

@genofire

This comment has been minimized.

Copy link
Contributor Author

commented Sep 8, 2018

Work carbons in singlechat? (Have not try to devices at the same time) - that would be another issue

@allo-

This comment has been minimized.

Copy link

commented Sep 8, 2018

OMEMO works for me now after some fiddling with the other clients until all keys are correctly stored on the server.

With carbons I have the problem, that I cannot see the ones from gajim. To gajim and from/to converstions work nicely. But this probably either deserves an own bug here or possibly one in the gajim bugtracker.

@genofire

This comment has been minimized.

Copy link
Contributor Author

commented Sep 8, 2018

i check it also again - reading OMEMO works 👍
now only writing is nessesary

@jcbrand jcbrand added the Feature label Sep 10, 2018

@jcbrand jcbrand changed the title OMEMO on muc / chatrooms OMEMO in a MUC Sep 10, 2018

jcbrand added a commit that referenced this issue Dec 14, 2018

Always render the OMEMO lock icon
When OMEMO isn't possible, render it as grey.

This change makes OMEMO for MUCs easier, since there I anticipate that
OMEMO support might change dynamically based on who enters/exits the
room.

updates #1180

jcbrand added a commit that referenced this issue Dec 14, 2018

jcbrand added a commit that referenced this issue Dec 17, 2018

jcbrand added a commit that referenced this issue Dec 17, 2018

jcbrand added a commit that referenced this issue Dec 17, 2018

jcbrand added a commit that referenced this issue Dec 17, 2018

jcbrand added a commit that referenced this issue Dec 17, 2018

jcbrand added a commit that referenced this issue Dec 18, 2018

jcbrand added a commit that referenced this issue Dec 18, 2018

Add test for sending/receiving MUC OMEMO messages
While adding support for MUCs, I refactored converse-omemo somewhat to move functions
out of `overrides` and to use async/await

Updates #1180

jcbrand added a commit that referenced this issue Dec 19, 2018

jcbrand added a commit that referenced this issue Dec 19, 2018

Add test for sending/receiving MUC OMEMO messages
While adding support for MUCs, I refactored converse-omemo somewhat to move functions
out of `overrides` and to use async/await

Updates #1180

jcbrand added a commit that referenced this issue Dec 19, 2018

jcbrand added a commit that referenced this issue Dec 19, 2018

Add test for sending/receiving MUC OMEMO messages
While adding support for MUCs, I refactored converse-omemo somewhat to move functions
out of `overrides` and to use async/await

Updates #1180
@trasba

This comment has been minimized.

Copy link

commented Dec 19, 2018

Work carbons in singlechat? (Have not try to devices at the same time) - that would be another issue

Hi,

I have exactly this issue. Setup is prosody server with xep-0280 'carbons'
It is working for unencrypted messages. OMEMO encrypted messages can be received and decrypted but I can't send any encrypted messages. I get:

Sorry, could not send the message due to an error. Cannot read property 'prekeys' of undefined

Setup is both clients are conversations, server is prosody and one of the clients is logged in with conversejs in parallel.

EDIT: Curiously it is now working I just deactivated carbons now on the server and activated it again. Then I got the error message constantly I logged in from the conversejs website and than it worked. It is now also working from my conversejs website. Very strange but ok...
So just to let you know it is working

jcbrand added a commit that referenced this issue Dec 20, 2018

jcbrand added a commit that referenced this issue Dec 20, 2018

jcbrand added a commit that referenced this issue Dec 20, 2018

jcbrand added a commit that referenced this issue Dec 20, 2018

Add test for sending/receiving MUC OMEMO messages
While adding support for MUCs, I refactored converse-omemo somewhat to move functions
out of `overrides` and to use async/await

Updates #1180

jcbrand added a commit that referenced this issue Dec 20, 2018

jcbrand added a commit that referenced this issue Dec 20, 2018

jcbrand added a commit that referenced this issue Dec 20, 2018

Add test for sending/receiving MUC OMEMO messages
While adding support for MUCs, I refactored converse-omemo somewhat to move functions
out of `overrides` and to use async/await

Updates #1180
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.