-
-
Notifications
You must be signed in to change notification settings - Fork 764
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
XEP-0384: OMEMO Encryption [$40 awarded] #497
Comments
would be great getting this ! |
+1 |
I am very interested in this, too. |
I'm also very interested. That's really a great feature. |
+1 |
See also OMEMO.js at cryptocat/cryptocat#178 |
What are the blockers you have that are preventing implimentation of OMEMO? |
@herbsmn I currently don't have the time for it. |
The XEP is now release http://xmpp.org/extensions/xep-0384.html |
There is a pending GSOC Proposal for this feature. |
Maybe someone want to implement OMEMO support for bounty ? We can discuss ) |
Unfortunately converse.js didn't get any GSOC students this year. There were three applications, but none of them made the cut. The decision was made by the XSF foundation and myself. What also played a role was that I wasn't able to find a backup mentor to help me this year. This means that there's nobody working on OMEMO currently. @ignatdoc Why don't you simply post a bounty on bountysource? The link is in the ticket description. The money doesn't get subtracted unless and until this ticket gets closed. This applies to anyone else who wants to see this ticket move forward. |
jsxc has a new OMEMO plugin: I hope this helps since it's written in javascript. |
Conversations now is encrypting with OMEMO by default, what can break communication. Would be nice to have this now also in Converse.js ! |
Add 3rd party dependencies updates #497
When receiving a PreKeySignalMessage, then a prekey has been chosen and should now be removed from the list of available prekeys in the bundle, so that a different device doesn't choose it as well. AFAICT, libsignal removes the prekey, so it's then up to us to regenerate it and republish our bundle. updates #497
OMEMO support has been added. Tested with Conversations. |
how do you enable it? |
libsignal needs to be loaded and available. Then you will see a lock icon in the chat toolbar. |
okay got it, just do a Is there any way of qrcode to scan for Conversations and co? |
I wanted to try OMEMO from https://inverse.chat/ or https://conversejs.org/. |
@MatthiasKauer Should be fixed now, thanks for reporting. |
sounds easy, but sorry, I could not find any lock icon, neither at https://inverse.chat/ nor at https://conversejs.org/ although libsignal is included and available. |
It's fixed as far as I can tell.
I happily used inverse.chat yesterday.
…On October 23, 2018 4:22:50 PM GMT+08:00, MaggusK ***@***.***> wrote:
> @MatthiasKauer Should be fixed now, thanks for reporting.
sounds easy, but sorry, I could not find any lock icon, neither at
https://inverse.chat/ nor at https://conversejs.org/ although libsignal
is included an available.
(I use firefox 60.1.0esr (64-bit) on RHEL 6.10)
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#497 (comment)
|
|
obviously OMEMO encryption is only supported for XMPP IDs of the same server. I created a new conversejs ID and with this encryption works on conversejs.org. But also the conversejs ID does not work on inverse.chat as all my other IDs don't. |
No, this is not true. OMEMO encryption is client-based and largely independent of the server (as long as it is modern enough to implement PEP).
Both users need to use an OMEMO compliant client. What did the other user use? |
I always chat with the same other jabber.de user that is using conversations. If I log in with my new conversejs.org ID it works. As you can see on the screenshot above it also doesn't decrypt the received OMEMO encrypted messages from conversations. |
@MaggusK I don't know. Maybe you have old cached JavaScript files? Clear your cache and then check again. |
@jcbrand : I found out, there is also a jabber webchat at https://chat.jabber.de/ (using conversejs). |
How do I enable omemo in converse? Every message is unencrypted for me. Edit: I used an untrusted device as option. But with a trusted device it still does not work in a group channel. Why? |
@NicoHood Not for groups yet. Just 1:1 for now. |
But then this list ist wrong: |
Is there any plan for converse.js to support group chat and OMEMO? |
@jcbrand: OMEMO works in groups if all users have OMEMO keys of all users in the group. Can you look it? |
Request for adding support for omemo encryption http://conversations.im/xeps/multi-end.html
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The $40 bounty on this issue has been claimed at Bountysource.
The text was updated successfully, but these errors were encountered: