E2EE OMEMO support
Can you add OMEMO?
- https://github.com/Syndace/python-omemo
- https://github.com/Syndace/python-twomemo
- https://github.com/Syndace/python-oldmemo
Note that it can be removed:
- https://github.com/Syndace/python-omemo-backend-signal
Thanks in advance.
These look like pure python libraries. Why do you think they don't already work? What errors do you get?
This might be a support request rather than a feature request.
@Julian-O: The XEP-0384 has been updated several times, several years ago and it is finished for:
- https://github.com/Syndace/python-omemo-backend-signal
Now it is:
- https://github.com/Syndace/python-omemo
- https://github.com/Syndace/python-twomemo
- https://github.com/Syndace/python-oldmemo (the original OMEMO)
Diff Tool:
- 0.3.0 to current: http://www.aptest.com/standards/htmldiff/htmldiff.pl?oldfile=https://xmpp.org/extensions/attic/xep-0384-0.3.0.html&newfile=https://xmpp.org/extensions/xep-0384.html
- 0.8.3 to current: http://www.aptest.com/standards/htmldiff/htmldiff.pl?oldfile=https://xmpp.org/extensions/attic/xep-0384-0.8.3.html&newfile=https://xmpp.org/extensions/xep-0384.html
- 0.8.2 to 0.8.3: http://www.aptest.com/standards/htmldiff/htmldiff.pl?oldfile=https://xmpp.org/extensions/attic/xep-0384-0.8.2.html&newfile=https://xmpp.org/extensions/attic/xep-0384-0.8.3.html
- 0.8.1 to 0.8.2: http://www.aptest.com/standards/htmldiff/htmldiff.pl?oldfile=https://xmpp.org/extensions/attic/xep-0384-0.8.1.html&newfile=https://xmpp.org/extensions/attic/xep-0384-0.8.2.html
- 0.8.0 to 0.8.1: http://www.aptest.com/standards/htmldiff/htmldiff.pl?oldfile=https://xmpp.org/extensions/attic/xep-0384-0.8.0.html&newfile=https://xmpp.org/extensions/attic/xep-0384-0.8.1.html
- 0.7.0 to 0.8.0: http://www.aptest.com/standards/htmldiff/htmldiff.pl?oldfile=https://xmpp.org/extensions/attic/xep-0384-0.7.0.html&newfile=https://xmpp.org/extensions/attic/xep-0384-0.8.0.html
- 0.6.0 to 0.7.0: http://www.aptest.com/standards/htmldiff/htmldiff.pl?oldfile=https://xmpp.org/extensions/attic/xep-0384-0.6.0.html&newfile=https://xmpp.org/extensions/attic/xep-0384-0.7.0.html
- 0.5.0 to 0.6.0: http://www.aptest.com/standards/htmldiff/htmldiff.pl?oldfile=https://xmpp.org/extensions/attic/xep-0384-0.5.0.html&newfile=https://xmpp.org/extensions/attic/xep-0384-0.6.0.html
- 0.4.0 to 0.5.0: http://www.aptest.com/standards/htmldiff/htmldiff.pl?oldfile=https://xmpp.org/extensions/attic/xep-0384-0.4.0.html&newfile=https://xmpp.org/extensions/attic/xep-0384-0.5.0.html
- 0.3.0 to 0.4.0: http://www.aptest.com/standards/htmldiff/htmldiff.pl?oldfile=https://xmpp.org/extensions/attic/xep-0384-0.3.0.html&newfile=https://xmpp.org/extensions/attic/xep-0384-0.4.0.html
Note: There is "XEP-0454: OMEMO Media sharing" too:
- https://xmpp.org/extensions/xep-0454.html
Let me see if I can summarise.
There was a PyPI library called omemo. It was a pure Python library, but depended on x3dh and cryptography. A recipe was added for v0.11.0 to python-for-android. I believe that recipe just makes sure that the dependencies are recognised.
Since then, omemo has been split into three different libraries: python-omemo and python-twomemo and python-old-omemo. They remain pure Python libraries, but depend on different libraries - libsodium (which has a recipe) and libxeddsa which doesn't.
You are asking for a recipe for these three libraries. I would suggest that we see if we can merely support libxeddsa and see if we can then use these pure Python packages without recipes.
Meanwhile, there is another related project on PyPI: omemo-backend-signal. Its GitHub has been archived. You are asking for the recipe to be removed; I can't see the harm in letting the old code continue to work.