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

feature request for omemo #63

Open
muzirian-zz opened this issue Oct 6, 2015 · 14 comments
Open

feature request for omemo #63

muzirian-zz opened this issue Oct 6, 2015 · 14 comments

Comments

@muzirian-zz
Copy link

Request for adding support for omemo encryption http://conversations.im/xeps/multi-end.html

@tbeitter
Copy link

tbeitter commented Nov 3, 2015

+1

2 similar comments
@rorycornell
Copy link

+1

@tdschwarz
Copy link

+1

@gofabian
Copy link

gofabian commented Jan 9, 2016

Omemo would be great. That's the only thing missing.

@capstab
Copy link

capstab commented Jan 19, 2016

I would use kaiwa instandly if there would be some kind of message encryption. I really would like it if i can encryption messages with Omemo.

@gmoretti
Copy link

+1

@GrimKriegor
Copy link

Gonna have to BUMP.
Any news on this feature?

@borghal
Copy link

borghal commented Dec 22, 2016

+1 Please!

@Vertux
Copy link

Vertux commented Feb 6, 2017

+1

@bill-mcgonigle
Copy link

Looks like with ChatSecure 4 on iOS recently released we have OMEMO on all major client-side platforms. It would be nice to have it on the web but we might just turn off our web interface for now since the trade-offs are now different.

perhaps useful:
http://xmpp.org/extensions/xep-0384.html
https://github.com/cryptocat/cryptocat/blob/master/src/js/omemo.js
https://github.com/joebandenburg/libaxolotl-javascript
jsxc/jsxc#228

@hubgitbb
Copy link

+1

@orbitz
Copy link

orbitz commented Jun 8, 2019

Any updates on the possibility of this?

@rorycornell
Copy link

rorycornell commented Jun 8, 2019 via email

@raspbeguy
Copy link

I would really like this feature too.

But people have to understand that, except if the encryption is made at client JS level, it wouldn't be end-to-end encryption, but end-to-webclient encryption, which is totally fine for me because I trust my own web infrastructure. But people using public instances of the webclient should be aware of this little inconsistency.

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

No branches or pull requests