XEP-0384: OMEMO Encryption #497

Open
muzirian opened this Issue Oct 6, 2015 · 18 comments

Comments

Projects
None yet
@muzirian

muzirian commented Oct 6, 2015

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.

@jcbrand jcbrand added the enhancement label Oct 7, 2015

@jcbrand jcbrand changed the title from feature request for omemo to XEP-xxxx: OMEMO Encryption Oct 7, 2015

@lovetox

This comment has been minimized.

Show comment
Hide comment
@lovetox

lovetox Jan 13, 2016

would be great getting this !

lovetox commented Jan 13, 2016

would be great getting this !

@tristan-k

This comment has been minimized.

Show comment
Hide comment

+1

@devdan

This comment has been minimized.

Show comment
Hide comment
@devdan

devdan Jan 18, 2016

I am very interested in this, too.

devdan commented Jan 18, 2016

I am very interested in this, too.

@nick4me

This comment has been minimized.

Show comment
Hide comment
@nick4me

nick4me Jan 18, 2016

I'm also very interested. That's really a great feature.

nick4me commented Jan 18, 2016

I'm also very interested. That's really a great feature.

@rasos

This comment has been minimized.

Show comment
Hide comment
@rasos

rasos May 29, 2016

+1
would fit perfectly with the Conversations Android App, which also supports omemo

rasos commented May 29, 2016

+1
would fit perfectly with the Conversations Android App, which also supports omemo

@GreenLunar

This comment has been minimized.

Show comment
Hide comment
@GreenLunar

GreenLunar Aug 6, 2016

Contributor

See also OMEMO.js at cryptocat/cryptocat#178

Contributor

GreenLunar commented Aug 6, 2016

See also OMEMO.js at cryptocat/cryptocat#178

@GreenLunar GreenLunar referenced this issue in nylira/prism-break Aug 6, 2016

Closed

Add OMEMO to /protocols/omemo #1476

@herbsmn

This comment has been minimized.

Show comment
Hide comment
@herbsmn

herbsmn Sep 9, 2016

What are the blockers you have that are preventing implimentation of OMEMO?

herbsmn commented Sep 9, 2016

What are the blockers you have that are preventing implimentation of OMEMO?

@jcbrand

This comment has been minimized.

Show comment
Hide comment
@jcbrand

jcbrand Sep 9, 2016

Member

@herbsmn I currently don't have the time for it.

Member

jcbrand commented Sep 9, 2016

@herbsmn I currently don't have the time for it.

@3615pipou

This comment has been minimized.

Show comment
Hide comment

The XEP is now release http://xmpp.org/extensions/xep-0384.html

@jcbrand jcbrand changed the title from XEP-xxxx: OMEMO Encryption to XEP-0384: OMEMO Encryption Feb 14, 2017

@jcbrand

This comment has been minimized.

Show comment
Hide comment
@jcbrand

jcbrand Feb 14, 2017

Member

There is a pending GSOC Proposal for this feature.

Member

jcbrand commented Feb 14, 2017

There is a pending GSOC Proposal for this feature.

@ignatdoc

This comment has been minimized.

Show comment
Hide comment
@ignatdoc

ignatdoc May 24, 2017

Maybe someone want to implement OMEMO support for bounty ? We can discuss )

Maybe someone want to implement OMEMO support for bounty ? We can discuss )

@jcbrand

This comment has been minimized.

Show comment
Hide comment
@jcbrand

jcbrand Jun 27, 2017

Member

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.

Member

jcbrand commented Jun 27, 2017

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.

@plambe

This comment has been minimized.

Show comment
Hide comment
@plambe

plambe Mar 20, 2018

jsxc has a new OMEMO plugin:
https://github.com/jsxc/jsxc-plugin-omemo

I hope this helps since it's written in javascript.

plambe commented Mar 20, 2018

jsxc has a new OMEMO plugin:
https://github.com/jsxc/jsxc-plugin-omemo

I hope this helps since it's written in javascript.

@Mrfuyu

This comment has been minimized.

Show comment
Hide comment
@Mrfuyu

Mrfuyu Mar 27, 2018

Conversations now is encrypting with OMEMO by default, what can break communication. Would be nice to have this now also in Converse.js !

Mrfuyu commented Mar 27, 2018

Conversations now is encrypting with OMEMO by default, what can break communication. Would be nice to have this now also in Converse.js !

jcbrand added a commit that referenced this issue May 11, 2018

updates #497
Initial work on adding OMEMO support

jcbrand added a commit that referenced this issue May 11, 2018

updates #497
Initial work on adding OMEMO support

jcbrand added a commit that referenced this issue May 11, 2018

updates #497
Initial work on adding OMEMO support

jcbrand added a commit that referenced this issue May 12, 2018

updates #497
Initial work on adding OMEMO support

jcbrand added a commit that referenced this issue May 12, 2018

updates #497
Various fixes to code checking for server and contact client support

jcbrand added a commit that referenced this issue May 12, 2018

updates #497
Initial work on adding OMEMO support

jcbrand added a commit that referenced this issue May 12, 2018

updates #497
Various fixes to code checking for server and contact client support

jcbrand added a commit that referenced this issue May 12, 2018

Add missing declaration and don't run OTR tests
Add 3rd party dependencies

updates #497

jcbrand added a commit that referenced this issue May 12, 2018

jcbrand added a commit that referenced this issue May 12, 2018

updates #497
Initial work on adding OMEMO support

jcbrand added a commit that referenced this issue May 12, 2018

updates #497
Various fixes to code checking for server and contact client support

jcbrand added a commit that referenced this issue May 12, 2018

Add missing declaration and don't run OTR tests
Add 3rd party dependencies

updates #497

jcbrand added a commit that referenced this issue May 12, 2018

jcbrand added a commit that referenced this issue May 12, 2018

Add test that the OMEMO toolbar button renders
Fix and improve accordingly. updates #497

jcbrand added a commit that referenced this issue May 12, 2018

Add test that the OMEMO toolbar button renders
Fix and improve accordingly. updates #497

jcbrand added a commit that referenced this issue May 12, 2018

Add test that the OMEMO toolbar button renders
Fix and improve accordingly. updates #497

jcbrand added a commit that referenced this issue May 13, 2018

updates #497
Initial work on adding OMEMO support

jcbrand added a commit that referenced this issue May 13, 2018

updates #497
Various fixes to code checking for server and contact client support

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

updates #497
Various fixes to code checking for server and contact client support

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

Add missing declaration and don't run OTR tests
Add 3rd party dependencies

updates #497

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

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

Add test that the OMEMO toolbar button renders
Fix and improve accordingly. updates #497

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

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

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

When generating a device id, check whether it already exists
and if so, generate a new one.

To do so we have to change the order of events.

1. first we fetch our device list
2. then we generate our bundle info (if necessary)
3. then we update our device list (if necessary)
4. then we publish our bundle

updates #497

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

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

More OMEMO work
- Implement storage interface required by libsignal
- Add some skeleton code for building sessions and sending encrypted messages

updates #497

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

Add a test to check that device lists get updated via PEP
And fix various bugs in the process.

updates #497

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

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

Add a test to check that device lists get updated via PEP
And fix various bugs in the process.

updates #497

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

Add a test to check that device lists get updated via PEP
And fix various bugs in the process.

updates #497

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

Test that device lists can get updated via PEP
Fix various bugs in the process.

updates #497

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

Test that bundles can be updated via PEP
Fix bugs in the process

udpates #497

jcbrand added a commit that referenced this issue May 21, 2018

Test that bundles can be updated via PEP
Fix bugs in the process

udpates #497

jcbrand added a commit that referenced this issue May 23, 2018

updates #497
Initial work on adding OMEMO support

jcbrand added a commit that referenced this issue May 23, 2018

updates #497
Various fixes to code checking for server and contact client support

jcbrand added a commit that referenced this issue May 23, 2018

Add missing declaration and don't run OTR tests
Add 3rd party dependencies

updates #497

jcbrand added a commit that referenced this issue May 23, 2018

jcbrand added a commit that referenced this issue May 23, 2018

Add test that the OMEMO toolbar button renders
Fix and improve accordingly. updates #497

jcbrand added a commit that referenced this issue May 23, 2018

jcbrand added a commit that referenced this issue May 23, 2018

jcbrand added a commit that referenced this issue May 23, 2018

When generating a device id, check whether it already exists
and if so, generate a new one.

To do so we have to change the order of events.

1. first we fetch our device list
2. then we generate our bundle info (if necessary)
3. then we update our device list (if necessary)
4. then we publish our bundle

updates #497

jcbrand added a commit that referenced this issue May 23, 2018

jcbrand added a commit that referenced this issue May 23, 2018

More OMEMO work
- Implement storage interface required by libsignal
- Add some skeleton code for building sessions and sending encrypted messages

updates #497

jcbrand added a commit that referenced this issue May 23, 2018

jcbrand added a commit that referenced this issue May 23, 2018

Test that device lists can get updated via PEP
Fix various bugs in the process.

updates #497

jcbrand added a commit that referenced this issue May 23, 2018

Test that bundles can be updated via PEP
Fix bugs in the process

udpates #497
@albjeremias

This comment has been minimized.

Show comment
Hide comment
@albjeremias

albjeremias Jun 25, 2018

how is the progress on this? what needs to be done? i see some commits... :)

how is the progress on this? what needs to be done? i see some commits... :)

@jcbrand

This comment has been minimized.

Show comment
Hide comment
@jcbrand

jcbrand Jun 25, 2018

Member

Most of session and key management is implemented. Actual encryption of messages is not yet done.

Member

jcbrand commented Jun 25, 2018

Most of session and key management is implemented. Actual encryption of messages is not yet done.

@albjeremias

This comment has been minimized.

Show comment
Hide comment
@jcbrand

This comment has been minimized.

Show comment
Hide comment
@jcbrand

jcbrand Jun 25, 2018

Member

yes

Member

jcbrand commented Jun 25, 2018

yes

jcbrand added a commit that referenced this issue Jul 21, 2018

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