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

yaxim client OMEMO ("better" than OTR) #197

Open
solarnoid opened this issue May 22, 2016 · 17 comments
Open

yaxim client OMEMO ("better" than OTR) #197

solarnoid opened this issue May 22, 2016 · 17 comments

Comments

@solarnoid
Copy link

solarnoid commented May 22, 2016

#82 (Support OTR encryption)

Will there be client support for OMEMO for interop with other supporting clients like Conversations

@ge0rg
Copy link
Collaborator

ge0rg commented May 22, 2016

Yes I have plans for OMEMO. Somebody just needs to implement it.

@ge0rg ge0rg added this to the 1.0 milestone Dec 18, 2016
@vanitasvitae
Copy link

I'm working on a Smack module as part of my bachelors thesis. This might solve the issue when its done :)

@Flowdalic
Copy link

Releated Smack issue: https://issues.igniterealtime.org/browse/SMACK-743

@ghost
Copy link

ghost commented Jun 4, 2017

Maybe, after all, OTR is better? For OMEMO, the server must support it.
For example, I encrypt OTR messages with users Mail.Ru Agent via XMPP transport, and with OMEMO, it seems, so impossible.

@vanitasvitae
Copy link

@Urgant OTR does not suppport offline messages, as well as mutliple recipient devices at once.

Its true, that the server has support PubSub, but PubSub support becomes more and more a criteria for a "good" server.

Btw:

I'm working on a Smack module as part of my bachelors thesis. This might solve the issue when its done :)

Smack does now have OMEMO support :)

@ghost
Copy link

ghost commented Jun 4, 2017

I do not need offline messages, but with users of other protocols I sometimes communicate through XMPP transports and I would like this communication to be encrypted. Now we use OTR. How can OMEMO do this?

@vanitasvitae
Copy link

OMEMO cannot do this, but what you describe is definitelly what I'd consider an exotic usecase. Also OMEMO and OTR are not mutually exclusive. That means you can switch between them :)

@ghost
Copy link

ghost commented Jun 4, 2017

Ah, if only that. But I would say that exotic is more like XMPP. The same Mail.Ru Agent is used every month by 18.8 million people in the world. And with them you need to be able to encrypt the correspondence through XMPP transport. And in Yaxim there is no OTR.

@ge0rg
Copy link
Collaborator

ge0rg commented Jun 17, 2017

@Urgant while I can see your reasoning, OTR is a real mess when any person involved uses more than one client. This issue is strictly about OMEMO. Please read up in #82 why yaxim doesn't have and won't have support for OTR.

@mvhulten
Copy link

OMEMO would be a great addition. If it were included, yaxim would be for me a good, light alternative for Conversations.

@d668
Copy link

d668 commented Dec 24, 2018

so no OMEMO at the moment?

@ge0rg
Copy link
Collaborator

ge0rg commented Dec 24, 2018

There is work on moving from my ancient rotting Smack fork to Smack4.3 right now. If there is an easy-to-plug-in OMEMO implementation in that, it might come sooner than you think. But right now, there is zero code for OMEMO support in yaxim, and I have zero time to pursuit that.

@vanitasvitae
Copy link

@ge0rg I'm happy to assist you with Smacks OMEMO implementation :) I'm sure that the code would benefit from some client developers feedback!

@lord-aerion
Copy link

Is there any progress on this issue?

@ge0rg
Copy link
Collaborator

ge0rg commented Aug 14, 2020

Sorry, I don't have the time to work on it right now. PRs are welcome, though ;)

@lord-aerion
Copy link

I wish I could help, but I have zero coding skills. Willing to help in other ways though, like testing.

Have you been able to find some time since your last message?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants