Hi, I'm writing this to both otr-dev and . Please CC both lists on replying.
I recently came across an issue about the addressing of conversation contexts in the XMPP protocol. IMO, the most sensible way to identify a user in a context is to use the full jid (ie. with resource: "[EMAIL PROTECTED]/resource"), because you could have multiple conversations to one user, where one resource knows OTR and another doesn't. OTOH, we have a problem when the local user does not know the resources of the remote user for any reason. This can be the case when they are not subscribed to each other, or when the remote user is invisible. The remote user could start an OTR session and the stanza would contain a resource (from="[EMAIL PROTECTED]/resource"). Now the local user receives the message and creates a context for "[EMAIL PROTECTED]/resource". But since the local user does not know about any resources, the messages he sends have to be sent to "[EMAIL PROTECTED]". The OTR lib now checks for the context with the remote user "[EMAIL PROTECTED]" and will find nothing, as it only knows the full JID. So, it will not encrypt the sent message to the remote user, because it does not find any conversation context. The remote user will see the message as "not encrypted though we should be encrypted", because he started the encrypted conversation. Any ideas/thoughts on how to handle this case? Kjell
signature.asc
Description: This is a digitally signed message part
_______________________________________________ JDev mailing list FAQ: http://www.jabber.org/discussion-lists/jdev-faq Forum: http://www.jabberforum.org/forumdisplay.php?f=20 Info: http://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: [EMAIL PROTECTED] _______________________________________________
