#965 Publishing Options in pubsub

Reporter Michel Le Bihan
Owner Nobody
Stars ★★★★★★ (21)  
  • Status-New
  • Type-Enhancement
  • Priority-Medium
  1. Michel Le Bihan on

    Description of feature: https://gultsch.de/files/xep-0060.html#publisher-publish-options Motivation: Allows for OMEMO with non-contacts or contacts without presence authorization.

  2. Tito on

    Has this been implemented yet?

  3. Michel Le Bihan on

    Link to updated XEP on xmpp.org: https://xmpp.org/extensions/xep-0060.html#publisher-publish-options

  4. Xmpp Texting: FTW on


  5. Anonymous on

    XEP-0060 is supported by Prosody since a long time ago, as a component. I think you just need to enable it. See https://prosody.im/doc/pubsub, you need yet another extra subdomain and should include it to your server certificate.

  6. Anonymous on

    Okay, I see the issue. The problem here is PubSub component in Prosody doesn't support Section 7.1.5 (a.k.a. publish-options) of XEP-0060, which affects the usability of OMEMO. Anyone has the plan to implement it?

  7. Zash on

    Publishing Options alone will not help with your OMEMO use case. The actual feature you are after is called access models. https://xmpp.org/extensions/xep-0060.html#accessmodels

  8. Anonymous on

    So to allow for OMEMO with non-contacts or contacts without presence authorization we don't need publishing-options? Issue link by Xmpp Texting: FTW says it is necessary

  9. Andrey on

    Just announced on prosody MUC: https://github.com/iNPUTmice/omemo_all_access > Traditionally OMEMO encrypted messages could only be exchanged after gaining mutual presence subscription due to the OMEMO key material being stored in PEP. > > XEP-0060 defines a method of changing the access model of a PEP node from presence to open. However Prosody does not yet support access models on PEP nodes. > > This module disables access control for all OMEMO PEP nodes (=all nodes in the namespace of eu.siacs.conversations.axolotl.*), giving everyone access to the OMEMO key material and allowing them to start OMEMO sessions with users on this server.

  10. Andrey on

    BTW, this feature could be mission critical important: e.g. Movim migrated to another jabber server software [1] and the only reason against prosody was this issue: > TJ: I chose to move back to ejabberd, because Metronome was getting outdated and Prosody was not “Pubsub ready”. [1] https://blog.process-one.net/movim-migrates-its-official-server-to-ejabberd/

New comment