[ejabberd] MUC handling of non-groupchat messages

Peter Saint-Andre stpeter at stpeter.im
Tue Jan 8 02:24:21 MSK 2008


I have a report that ejabberd 1.1.3 or 1.1.4 will kick a MUC room 
occupant if the user sends a message to another occupant and the message 
is of type "error". For example consider the following exchange (JIDs 
changed slightly)...

<message type="groupchat"
          from="psi at conference.psi-im.org/foo"
          to="psi at conference.psi-im.org/bar"
          id="abcda">
   <body>This message is encrypted.</body>
   <x xmlns='jabber:x:encrypted'>
     big-encrypted-blob-here
   </x>
</message>

<message type="error"
          from="psi at conference.psi-im.org/bar"
          to="psi at conference.psi-im.org/foo"
          id="abcda">
   <body>
     [ERROR: This message is encrypted, and you are unable
     to decrypt it.]
   </body>
   <error type="modify" code="406" >
     <not-acceptable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/>
     <text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas">
       Unable to decrypt
     </text>
   </error>
</message>

At this point, ejabberd will kick user "bar" from the room. That seems 
unfriendly, and potentially even a DoS. I think it would be better for 
ejabberd to deliver the message or, if that is thought to be a problem, 
at least ignore the stanza.

Thoughts?

Peter

-- 
Peter Saint-Andre
https://stpeter.im/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7338 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.jabber.ru/pipermail/ejabberd/attachments/20080107/bd965f04/attachment.bin 


More information about the ejabberd mailing list