XSF Discussion - 2021-07-18


  1. southerntofu

    emus, hi where is a good place to discuss omemo.top project? :)

  2. emus

    southerntofu: in the issue repository I eould say

  3. southerntofu

    thanks https://github.com/bascht/omemo-top/issues/ for reference

  4. emus

    I know

  5. southerntofu

    (in case others wer ewondering)

  6. wuuko

    https://github.com/omemo İs this omemo codes?

  7. Daniel

    It's one code

  8. wuuko

    Where's all there?

  9. Daniel

    There is no central repository

  10. wuuko

    Where's the piece by piece? I'm asking because I don't know.

  11. southerntofu

    wuuko, there's man OMEMO implementations in many languages/libraries

  12. wuuko

    What do you mean? Can't we find the codes piece by piece?

  13. southerntofu

    wuuko, yes in dozens of different repositories, eg. slixmpp, smack, etc..

  14. southerntofu

    many clients have their own code/implementation

  15. southerntofu

    you can see it from https://omemo.top/

  16. wuuko

    > southerntofu wrote: > wuuko, yes in dozens of different repositories, eg. slixmpp, smack, etc.. > many clients have their own code/implementation > you can see it from https://omemo.top/ I didn't see the codes.

  17. Zash

    Source code? Or what are you looking for, exactly?

  18. Zash

    I'm guessing https://github.com/signalapp?q=libsignal-protocol is some of the available implementations of the low-level crypto stuff.

  19. wuuko

    > southerntofu wrote: > wuuko, yes in dozens of different repositories, eg. slixmpp, smack, etc.. > many clients have their own code/implementation > you can see it from https://omemo.top/ I didn't see the codes.

  20. wuuko

    > Zash wrote: > Source code? Or what are you looking for, exactly? Yes, omemo source code.

  21. MattJ

    OMEMO is a protocol, not software

  22. wuuko

    > MattJ wrote: > OMEMO is a protocol, not software Can't you get source code?

  23. MattJ

    I think you may be the same person who previously asked to see the source code for XMPP... the answer is the same for OMEMO :)

  24. wuuko

    > MattJ wrote: > I think you may be the same person who previously asked to see the source code for XMPP... the answer is the same for OMEMO :) how? Omemo doesn't have the source code, right?

  25. wuuko

    Can't it be source code?

  26. wuuko

    > MattJ wrote: > I think you may be the same person who previously asked to see the source code for XMPP... the answer is the same for OMEMO :) Yes ı am same man. I know the XMPP source code

  27. wuuko

    But omemo not

  28. Daniel

    wuuko: what are you trying to do? What's your goal

  29. wuuko

    > Daniel wrote: > wuuko: what are you trying to do? What's your goal I'm curious about the Omemo codes.

  30. Daniel

    Yes but what for. What are you trying to do

  31. Zash

    Here's the specification, if you just wanna read it: https://xmpp.org/extensions/xep-0384.html

  32. wuuko

    > Daniel wrote: > Yes but what for. What are you trying to do Aren't the codes public? It's just curiosity.

  33. Zash

    I'm extremely uncertain whether "codes" is the word you use for programming code or if this also includes the specifications.

  34. wuuko

    > Zash wrote: > I'm extremely uncertain whether "codes" is the word you use for programming code or if this also includes the specifications. Programming CODE

  35. Zash

    Linked to the libsignal stuff above.

  36. Daniel

    wuuko: https://github.com/Syndace/python-omemo

  37. wuuko

    https://github.com/Syndace/python-omemo https://xmpp.org/extensions/xep-0384.html Both of same?

  38. Daniel

    The first is source code. The second is a specification

  39. Zash

    Not all that familiar with all the codebases, but https://github.com/iNPUTmice/Conversations/tree/master/src/main/java/eu/siacs/conversations/crypto https://github.com/dino/dino/tree/master/plugins/omemo might be relevant.

  40. wuuko

    > Daniel wrote: > The first is source code. The second is a specification Specification?

  41. Daniel

    https://dictionary.cambridge.org/dictionary/english/specification?q=Specification

  42. wuuko

    Open source from what I've seen

  43. wuuko

    That's important

  44. Zash

    Specifications describe what the programming codes are supposed to say to each other, so that everyone understand each other.

  45. wuuko

    Now this is omemo source code https://github.com/Syndace/python-omemo This is info https://xmpp.org/extensions/xep-0384.html

  46. wuuko

    Right? I think I'm going to be opening a server soon, so I'm asking.

  47. Daniel

    Yes

  48. wuuko

    Can it change if it needs to change?

  49. wuuko

    Can it change if it needs to change?

  50. Daniel

    Yes

  51. wuuko

    Thanks

  52. wuuko

    How do I know the omemo on my phone is the same emomo in the code?

  53. Daniel

    By learning how to compile software and doing it yourself

  54. Zash

    Then by learning to build a compiler and building one yourself

  55. Zash

    And then build your own computer

  56. wuuko

    Is that the way it is in every messenger?

  57. Zash

    https://dl.acm.org/doi/pdf/10.1145/358198.358210

  58. wuuko

    > I wrote: > Is that the way it is in every messenger? I guess that's the way it is with every messenger.

  59. Zash

    Every messenger, every piece of software.

  60. Zash

    How do you know that anything is the way you think it is?

  61. wuuko

    > Zash wrote: > Every messenger, every piece of software. > How do you know that anything is the way you think it is? I dont know. :/

  62. Sam

    This conversation is your periodic reminder that everyone should read "Reflections on Trusting Trust": https://www.cs.cmu.edu/~rdriley/487/papers/Thompson_1984_ReflectionsonTrustingTrust.pdf

  63. Zash

    (that I just linked to 5 lines up)

  64. Sam

    hah, oops, ENOCTX

  65. me9

    What in the world is enoctx?

  66. Zash

    "No context" in the spirit of unix error codes (e.g see https://manpages.debian.org/buster/manpages-dev/errno.3.en.html#List_of_error_names )

  67. Zash

    POSIX even?

  68. jonas’

    yep posix

  69. me9

    Ah ok.

  70. wuuko

    I guess xmpp android client not uses Python omemo, where is the Android Python codes?

  71. wuuko

    > I wrote: > I guess xmpp android client not uses Python omemo, where is the Android Python codes?

  72. wuuko

    again me

  73. wuuko

    I guess Android xmpp clients not uses Python omemo. What is the omemo used by Android clients

  74. Sam

    Conversations has its own. I assume other things use Smack or babbler or whatever it was called

  75. wuuko

    Doesn't everyone use omemo?

  76. Sam

    I mean that they have their own implementations, not that they have their own encryption.

  77. Sam

    However, not everyo.e uses omemo either.

  78. wuuko

    > Sam wrote: > I mean that they have their own implementations, not that they have their own encryption. > However, not everyo.e uses omemo either. And do you know where the omemo codes are on the phone?

  79. Sam

    For what client?

  80. wuuko

    For example blabber

  81. Sam

    Blabber is a fork of Conversations, so I assume it's the same as this https://github.com/iNPUTmice/Conversations/tree/master/src/main/java/eu/siacs/conversations/crypto/axolotl

  82. wuuko

    İs axolotl same omemo?

  83. wuuko

    I was looking for "omemo", it didn't come out.

  84. Sam

    Yes, that's what an old version was called. I guess no one wanted to rename the files and clutter up the change log.

  85. wuuko

    Thanks, Sam.